From: Mark Kettenis <kettenis@chello.nl>
To: eliz@gnu.org
Cc: ford@vss.fsi.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Proper _to_regnum for DWARF on Cygwin
Date: Mon, 19 Apr 2004 19:59:00 -0000 [thread overview]
Message-ID: <200404191959.i3JJxQoQ000336@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <uk70clauk.fsf@elta.co.il> (message from Eli Zaretskii on 19 Apr 2004 08:50:59 +0200)
Date: 19 Apr 2004 08:50:59 +0200
From: Eli Zaretskii <eliz@elta.co.il>
> Date: Sun, 18 Apr 2004 20:38:38 +0200 (CEST)
> From: Mark Kettenis <kettenis@chello.nl>
>
> + /* We typically use DWARF-in-COFF with the dbx register numbering. */
> + set_gdbarch_dwarf_reg_to_regnum (gdbarch, i386_dbx_reg_to_regnum);
> + set_gdbarch_dwarf2_reg_to_regnum (gdbarch, i386_dbx_reg_to_regnum);
> }
Mark, doesn't this code above from i386_coff_init_abi contradict the
code further down (and the register mapping used by GCC), viz:
> + /* Use the SVR4 register numbering scheme for DWARF and DWARF 2. */
> + set_gdbarch_dwarf_reg_to_regnum (gdbarch, i386_svr4_reg_to_regnum);
> + set_gdbarch_dwarf2_reg_to_regnum (gdbarch, i386_svr4_reg_to_regnum);
? For DJGPP, at least, DWARF2-in-COFF uses i386_svr4_reg_to_regnum
register mapping, not i386_dbx_reg_to_regnum. Am I missing something
here?
Hmm. I very much agree with what Brian wrote in his follow-up
messages. I think DJGPP is doing the right thing using the SVR4
scheme for DWARF2 while staying backwards compatible for stabs. I'd
advise him to do the same for cygwin. If i386_coff_init_abi will be
gone, the comments aren't contradictiory anymore.
> + /* NOTE: kettenis/20040418: GCC does have two possible register
> + numbering schemes on the i386: dbx and SVR4. These schemes
> + differ in how they number %ebp, %esp, %eflags, and the
> + floating-point registers, and are implemented by the attays
^^^^^^
A typo.
I though I'd fixed that one :-(.
next prev parent reply other threads:[~2004-04-19 19:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 20:12 Brian Ford
2004-04-16 14:16 ` [PATCH] Proper _to_regnum for DWARF on cygwin (ping for Mark) Christopher Faylor
2004-04-16 16:26 ` Brian Ford
2004-04-16 18:50 ` Christopher Faylor
2004-04-21 15:28 ` [Patch ping] Re: COFF & mixed debug formats Brian Ford
2004-04-30 21:47 ` Brian Ford
2004-05-17 17:08 ` Brian Ford
2004-06-09 15:20 ` Brian Ford
2004-06-09 15:25 ` Daniel Jacobowitz
2004-06-09 21:24 ` Jim Blandy
2004-06-10 0:32 ` Christopher Faylor
2004-06-10 15:54 ` Brian Ford
2004-04-16 16:50 ` [PATCH] Proper _to_regnum for DWARF on Cygwin Mark Kettenis
2004-04-16 17:32 ` Brian Ford
2004-04-18 18:38 ` Mark Kettenis
2004-04-19 5:49 ` Eli Zaretskii
2004-04-19 16:21 ` Brian Ford
2004-04-19 20:49 ` Jim Blandy
2004-04-20 5:52 ` Eli Zaretskii
2004-04-19 19:59 ` Mark Kettenis [this message]
2004-04-19 23:46 ` Brian Ford
2004-04-20 16:30 ` Brian Ford
2004-04-30 20:19 ` 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=200404191959.i3JJxQoQ000336@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=eliz@gnu.org \
--cc=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