From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: hjl.tools@gmail.com
Cc: gdb-patches@sourceware.org
Subject: Re: PATCH: PR gdb/11265: "infor reg sse" doesn't work on Linux/x86-64
Date: Wed, 10 Feb 2010 21:00:00 -0000 [thread overview]
Message-ID: <201002102100.o1AL0RRT027674@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <20100210000116.GA23504@lucon.org> (hongjiu.lu@intel.com)
> Date: Tue, 9 Feb 2010 16:01:16 -0800
> From: "H.J. Lu" <hongjiu.lu@intel.com>
>
> Linux/x86-64 overides i386_register_reggroup_p with
> amd64_linux_register_reggroup_p, which calls
> default_register_reggroup_p. It makes Linux/x86-64 different from
> other x86-64 targets where "infor reg sse" works. This patch makes
> "infor reg sse" to work on Linux/x86-64 like other x86-64 targets. OK
> to install?
This is ok.
> 2010-02-09 H.J. Lu <hongjiu.lu@intel.com>
>
> PR gdb/11265
> * amd64-linux-tdep.c (amd64_linux_register_reggroup_p): Call
> i386_register_reggroup_p instead of default_register_reggroup_p.
prev parent reply other threads:[~2010-02-10 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 0:01 H.J. Lu
2010-02-10 21:00 ` Mark Kettenis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201002102100.o1AL0RRT027674@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox