Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@delorie.com>
To: kettenis@science.uva.nl
Cc: gdb@sources.redhat.com
Subject: Re: i386 register numbering
Date: Sat, 28 Jul 2001 05:14:00 -0000	[thread overview]
Message-ID: <200107281214.IAA07439@delorie.com> (raw)
In-Reply-To: <s3izo9pnuac.fsf@soliton.wins.uva.nl>

> From: Mark Kettenis <kettenis@science.uva.nl>
> Date: 28 Jul 2001 13:54:19 +0200
> 
> In GDB we have STAB_REG_TO_REGNUM, DWARF_REG_TO_REGNUM, etc.

Ah, I missed that additional layer of translation.  Thanks for
pointing it out.

> We have
> to provide a suitable definition for those in tm-i386.h.  However, the
> problem mentioned above makes it a bit tricky, since GCC always uses
> the same register numbering scheme, regardless of the actual debugging
> format.  Most ELF targets use the Dwarf scheme, even if the debugging
> format is stabs.  And it seems that DJGPP uses the "default" scheme,
> even if you ask for Dwarf 2 debugging info.

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...

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?

> I'm working on a patch, and I'll try to provide some reasonable
> defaults.  But most targets will have to override some of these
> defaults.

Thanks.


  reply	other threads:[~2001-07-28  5:14 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 [this message]
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

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=200107281214.IAA07439@delorie.com \
    --to=eliz@delorie.com \
    --cc=gdb@sources.redhat.com \
    --cc=kettenis@science.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