From: Mark Kettenis <kettenis@wins.uva.nl>
To: eliz@is.elta.co.il
Cc: gdb@sources.redhat.com
Subject: Re: i386 register numbering
Date: Sat, 28 Jul 2001 11:02:00 -0000 [thread overview]
Message-ID: <200107281802.f6SI27819117@delius.kettenis.local> (raw)
In-Reply-To: <200107281214.IAA07439@delorie.com>
Date: Sat, 28 Jul 2001 08:14:26 -0400
From: Eli Zaretskii <eliz@delorie.com>
DJGPP supports 3 debug info formats: COFF, stabs, and (lately) DWARF2;
the default is COFF. (Btw, I don't see any COFF_REG_TO_REGNUM.) I'm
guessing that no one (including myself ;-) bothered to review the
register naming scheme when support for stabs and DWARF2 was added...
With the patch that I just checked in, COFF and stabs should do the
right thing for DJGPP. DWARF2 will probably still give you the wrong
register. You might want to consider changing GCC such that it uses
the standard Dwarf renumbering for DWARF2. I don't think it really
matters since there aren't any native tools that you need to be
compatible with. On the other hand, using DWARF2 with a numbering
scheme that nobody else uses, might trigger some bugs.
If you don't change GCC you should probably override
DWARF2_REG_TO_REGNO in config/i386/tm-go32.h.
But there's something in your explanation that I don't get: if GCC
always uses the same scheme, no matter what the debug info, and since
all i386 targets use the same i386.h header which defines this scheme,
how come DJGPP can use something different than the other targets?
What am I missing?
Several GCC targets redefine DBX_REGISTER_NUMBER, see for example
linux.h in that same directory.
Mark
prev parent reply other threads:[~2001-07-28 11:02 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
2001-07-28 15:02 ` Mark Kettenis
2001-07-28 18:06 ` Andrew Cagney
2001-07-28 11:02 ` 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=200107281802.f6SI27819117@delius.kettenis.local \
--to=kettenis@wins.uva.nl \
--cc=eliz@is.elta.co.il \
--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