From: Andrew Cagney <ac131313@cygnus.com>
To: Mark Kettenis <kettenis@wins.uva.nl>
Cc: eliz@is.elta.co.il, gdb@sources.redhat.com
Subject: Re: i386 register numbering
Date: Sat, 28 Jul 2001 11:06:00 -0000 [thread overview]
Message-ID: <3B62FF33.2030807@cygnus.com> (raw)
In-Reply-To: <200107281741.f6SHfoN19109@delius.kettenis.local>
> For most of the registers on the i386, the raw and the cooked regnum
> will probably be the same. MMX will probably end up as a cooked
> registers some day (since they provide a different view on the
> standard FP registers). I cannot see how I can get rid of the convert
> stuff for the FP registers though. On the i386 the FP registers can
> contain a `float', `double' or `long double' but the internal
> representation in the FP register is identical. Turning every FP
> register into three cooked registers won't work since in the debug
> info they will all have the same register number [:-(] .
Regarding MMX, yes.
For the basic FP register, see my recent RFC post about adding
builtin_type_floatformat*:
http://sources.redhat.com/ml/gdb-patches/2001-07/msg00624.html
You're saying is that a i386 register is always formatted as
floatformat_i387_ext. Correct? Consequently, with the above change (and
related FIXMEs) in place, all the CONVERT* code could be deleted and
instead REGISTER_VIRTUAL_TYPE would just return
builtin_type_floatformat_i387_ext and GDB would internaly handle all the
conversion problems.
Andrew
next prev parent reply other threads:[~2001-07-28 11:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-28 3:14 Eli Zaretskii
2001-07-28 4:56 ` Mark Kettenis
2001-07-28 5:14 ` Eli Zaretskii
2001-07-28 8:12 ` Andrew Cagney
2001-07-28 10:41 ` Mark Kettenis
2001-07-28 11:06 ` Andrew Cagney [this message]
2001-07-28 15:02 ` Mark Kettenis
2001-07-28 18:06 ` Andrew Cagney
2001-07-28 11:02 ` Mark Kettenis
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=3B62FF33.2030807@cygnus.com \
--to=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=kettenis@wins.uva.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