From: Brian Ford <ford@vss.fsi.com>
To: gdb-patches@sources.redhat.com
Subject: ix86 PE/COFF DWARF register numbering (was Re: [PATCH] i386_stab_reg_to_regnum (4 <-> 5, ebp <-> esp))
Date: Mon, 19 Apr 2004 02:06:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.58.0404182045430.19804@thing1-200> (raw)
In-Reply-To: <2914-Sun18Apr2004194339+0300-eliz@gnu.org>
On Sun, 18 Apr 2004, Eli Zaretskii wrote:
> On 05 Apr 2004 at 17:44:14 -0500 Jim Blandy wrote:
> >
> > In fact, it looks to me as if DJGPP uses dbx_register_map for both
> > STABS and Dwarf 2. (Eli, is this right?)
>
> No, that's not what I see. The file /config/i386/djgpp.h in the GCC
> distribution says:
>
> #undef DBX_REGISTER_NUMBER
> #define DBX_REGISTER_NUMBER(n) \
> ((write_symbols == DWARF2_DEBUG) ? svr4_dbx_register_map[n] : dbx_register_map[n])
Aha!
> (This is from GCC 3.3.3 source distribution I find in the DJGPP
> repository.)
(We see in a later email that this distribution contains local patches
which have not been included in the FSF source base. That explains the
previous confusion.)
> So DJGPP uses svr4_dbx_register_map[] for DWARF-2, dbx_register_map[]
> otherwise.
Look Jim (does this sound like a bad Star Trek episode, or what? :), yet
another target that uses a different register map depending on the output
debugging format. And note that for DWARF 2, it uses the svr4 map, just
like every other ix86 target that I know of (except the current PE
proposal).
Now that the dbx_to_regnum bug has been fixed, it probably doesn't
matter, but I'm still leary of using a different register map for DWARF on
PE than every other ix86 target out there. I'd like to get this right up
front since now is the time to avoid possibly major compatibility
changes down the road.
What do you think? Should I revert the i386_coff_init_abi patch for
Cygwin and use the above method in gcc instead? I'm especially interested
in input from Jim Blandy, CGF, and Corinna.
Thanks.
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax: 314-551-8444
next prev parent reply other threads:[~2004-04-19 2:06 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 0:11 [PATCH] i386_stab_reg_to_regnum (4 <-> 5, ebp <-> esp) Brian Ford
2004-04-01 17:22 ` Jim Blandy
2004-04-01 18:00 ` Brian Ford
2004-04-01 21:29 ` Jim Blandy
2004-04-01 22:54 ` Brian Ford
2004-04-02 7:45 ` Eli Zaretskii
[not found] ` <Pine dot GSO dot 4 dot 58 dot 0404021000390 dot 21204 at thing1-200>
[not found] ` <2719-Fri02Apr2004213907+0300-eliz at gnu dot org>
[not found] ` <Pine dot GSO dot 4 dot 58 dot 0404021648050 dot 21204 at thing1-200>
2004-04-02 17:31 ` Brian Ford
2004-04-02 19:42 ` Eli Zaretskii
2004-04-02 23:15 ` Brian Ford
2004-04-03 9:08 ` Eli Zaretskii
2004-04-05 18:18 ` Jim Blandy
2004-04-05 21:57 ` Brian Ford
2004-04-18 16:33 ` Eli Zaretskii
2004-04-05 18:21 ` Jim Blandy
2004-04-05 22:46 ` Brian Ford
2004-04-18 17:00 ` Eli Zaretskii
2004-04-05 22:46 ` Jim Blandy
2004-04-05 23:19 ` Brian Ford
2004-04-05 23:38 ` Jim Blandy
2004-04-06 14:53 ` Brian Ford
2004-04-15 9:38 ` Eli Zaretskii
2004-04-06 23:24 ` Mark Kettenis
2004-04-07 16:25 ` Brian Ford
2004-04-07 18:02 ` Jim Blandy
2004-04-07 20:06 ` [PATCH] Rename i386_xxx_reg_to_regnum Brian Ford
2004-04-07 20:48 ` Jim Blandy
2004-04-07 21:06 ` Brian Ford
2004-04-07 21:41 ` Jim Blandy
2004-04-09 12:37 ` Mark Kettenis
2004-04-09 17:49 ` Brian Ford
2004-04-06 23:23 ` [PATCH] i386_stab_reg_to_regnum (4 <-> 5, ebp <-> esp) Mark Kettenis
2004-04-07 16:46 ` Jim Blandy
2004-04-18 16:48 ` Eli Zaretskii
2004-04-19 2:06 ` Brian Ford [this message]
2004-04-19 5:59 ` ix86 PE/COFF DWARF register numbering (was Re: [PATCH] i386_stab_reg_to_regnum (4 <-> 5, ebp <-> esp)) Eli Zaretskii
2004-04-19 16:34 ` ix86 PE/COFF DWARF register numbering Brian Ford
2004-04-19 12:42 ` [PATCH] i386_stab_reg_to_regnum (4 <-> 5, ebp <-> esp) Jim Blandy
2004-04-19 7:02 ` Eli Zaretskii
2004-04-02 19:33 ` Eli Zaretskii
2004-04-02 22:47 ` Brian Ford
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=Pine.GSO.4.58.0404182045430.19804@thing1-200 \
--to=ford@vss.fsi.com \
--cc=gdb-patches@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