From: Mark Kettenis <kettenis@chello.nl>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb@sources.redhat.com
Subject: Re: i386 register groups?
Date: Mon, 26 Aug 2002 13:47:00 -0000 [thread overview]
Message-ID: <86lm6tfiv7.fsf@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: Andrew Cagney's message of "Mon, 26 Aug 2002 15:30:21 -0400"
Andrew Cagney <ac131313@ges.redhat.com> writes:
> > On Mon, Aug 26, 2002 at 02:39:40PM -0400, Andrew Cagney wrote:
> >
> >> mxcsr 40 40 304 4 int general,all
> >
> >
> > With the other MMX registers, perhaps?
>
> Done (I wouldn't know an MMX register if I tripped over it :-).
And Daniel doesn't either ;-) (sorry Daniel). mxcsr is the SSE
control/status register, so the sse group seems more appropriate to
me ;-).
And while I'm at it, I don't think orig_eax belongs in the "generic"
group. It's some sort of OS-specific pseudo-register. We might
create a special register group for it, but putting it only in the
"all" group is fine by me. Fiddling with it is quite useless (and GDB
does it for you if it's needed).
And what do people think about moving the segment registers out of the
"general" group into their own group? If you don't program at the OS
level, you're not very likely to need them (although on Linux you
might be interested in %gs when debugging a multi-threaded program).
We could name the group "segment".
Mark
next prev parent reply other threads:[~2002-08-26 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-26 11:39 Andrew Cagney
2002-08-26 11:46 ` Daniel Jacobowitz
2002-08-26 12:30 ` Andrew Cagney
2002-08-26 13:47 ` Mark Kettenis [this message]
2002-08-26 13:51 ` Daniel Jacobowitz
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=86lm6tfiv7.fsf@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=ac131313@ges.redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.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