From: Daniel Jacobowitz <drow@mvista.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: Andrew Cagney <ac131313@ges.redhat.com>, gdb@sources.redhat.com
Subject: Re: i386 register groups?
Date: Mon, 26 Aug 2002 13:51:00 -0000 [thread overview]
Message-ID: <20020826205250.GA12224@nevyn.them.org> (raw)
In-Reply-To: <86lm6tfiv7.fsf@elgar.kettenis.dyndns.org>
On Mon, Aug 26, 2002 at 10:46:52PM +0200, Mark Kettenis wrote:
> 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 ;-).
Can't win 'em all.
> 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).
Agreed, only "all".
> 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".
GCC can now generate code that uses these, with the TLS extensions; I
think it'd be worthwhile to keep them. How useful having them is,
though, I don't know...
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-08-26 20:51 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
2002-08-26 13:51 ` Daniel Jacobowitz [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=20020826205250.GA12224@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@ges.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
/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