From: Jeff Epler <jepler@inetnebr.com>
To: gdb@cygnus.com
Subject: Re: MMX registers on x86?
Date: Mon, 12 Apr 1999 13:12:00 -0000 [thread overview]
Message-ID: <19990412151218.64916@falcon.inetnebr.com> (raw)
In-Reply-To: <npr9pp1y2u.fsf@zwingli.cygnus.com>
On Mon, Apr 12, 1999 at 01:40:57PM -0500, Jim Blandy wrote:
>
> > I know folks are talking about floating point support in gdb, but what
> > about MMX (including 3dnow) registers?
> >
> > In my work with 3dnow, I used as a solution a routine which stored the 8
> > mmx registers in memory, and I just examined that instead...
>
> I haven't heard of anyone else working on this. Write a patch! :)
I suspect that since one can already examine all 80 bits of the float
registers (?) that this is just a matter of writing the display code.
However, what do you do when the registers have so many different ways
of being looked at? These come to mind:
long double
float[2]
unsigned[4]
signed[4]
unsigned short[4]
short[4]
unsigned char[8]
signed char[8]
worse, one might wish for %mm0 to be a float[2] but %mm1 to be
unsigned[4]. The type letters used by "x" are useful for this, but I'm
not quite sure how they would apply to "print %mm0" or "info registers".
Jeff
--
\/ jepler@inetnebr.com http://incolor.inetnebr.com/jepler/ (0|1(01*0)*1)+
next prev parent reply other threads:[~1999-04-12 13:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-01 0:00 Jeff Epler
1999-04-12 11:41 ` Jim Blandy
1999-04-12 13:12 ` Jeff Epler [this message]
1999-04-14 14:14 ` J.T. Conklin
1999-04-14 15:18 ` J.T. Conklin
1999-04-14 16:43 ` Daniel Berlin
1999-04-14 17:59 ` Stan Shebs
1999-04-14 18:55 ` Stan Shebs
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=19990412151218.64916@falcon.inetnebr.com \
--to=jepler@inetnebr.com \
--cc=gdb@cygnus.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