From: Randolph Chung <randolph@tausq.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb@sources.redhat.com, dave@hiauly1.hia.nrc.ca,
brobecker@adacore.com
Subject: Re: Register numbers on hppa64
Date: Sat, 26 Nov 2005 16:52:00 -0000 [thread overview]
Message-ID: <43888F83.7090603@tausq.org> (raw)
In-Reply-To: <200511261518.jAQFIN2K022588@elgar.sibelius.xs4all.nl>
> Well, the ppc64 situation was a real mess, because the GCC people
> screwed up, and used *their* internal mapping instead of the
> officially documented numbers defined in the ELF ABI for DWARF2, and
> this mapping was also used for GCC's exception handling info (which is
> based on DWARF2). I'm not sure at all whether the issue has been
> resolved.
>
> For hppa64 the situation is much better since...
I thought one of the problems was that because the "dbx" and "dwarf"
mappings in gcc are different, it would use the dbx mappings in debug
info but the dwarf numbers elsewhere (e.g. for exception handling?). Is
that an issue at all?
>>Any comments or suggestions on how to sort this out? Should I just
>>change gdb to match what gcc outputs? Should we change gcc to match what
>>gdb expects? (safer?)
>
> ...we (GDB) are the ones that screwed up. Fortunately it's really
> easy to fix things. We just need to provide the appropriate
> xxx_reg_to_regnum functions in the acrhitecture vector.
Right, this does work for gcc, but I wonder if I'm breaking HP compiler
compatibility (which I cannot test...)
> Actually the fix seems to be partly implemented already: there's a
> #ifdeffed out hppa_dwarf_reg_to_regnum in hppa-linux-tdep.c. I think
> it should be moved to hppa-tdep.c, and a 64-bit version should be
> created.
I wrote that code... :) but I think it's actually wrong; for 32-bit we
have a 1:1 mapping between what gcc outputs for "dbx" register numbers
in dwarf debug mode and the gdb internal register numbering, so we
shouldn't need this mapping function for 32-bit.
> Anyway, see i386-tdep.c for a complicated example of how
> registers are mapped differently for several debugging formats and
> executable formats.
I believe HP compilers for hppa64-hpux also use dwarf; I don't see where
the register numbering is documented in the ABI. I can easily implement
a hppa64_dwarf_reg_to_regnum method, but I need to know if all hppa64
compilers have the same view of register numbers.
randolph
next prev parent reply other threads:[~2005-11-26 16:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200511260253.jAQ2rP7Z021130@hiauly1.hia.nrc.ca>
2005-11-26 9:23 ` Randolph Chung
2005-11-26 15:54 ` Mark Kettenis
2005-11-26 16:52 ` Randolph Chung [this message]
2005-11-26 17:32 ` Mark Kettenis
2005-11-26 18:50 ` John David Anglin
2005-11-27 16:30 ` Randolph Chung
2005-11-26 17:34 ` John David Anglin
2005-11-26 17:20 ` John David Anglin
2005-11-26 17:13 ` John David Anglin
2005-11-26 17:52 ` Mark Kettenis
2005-11-26 18:00 ` John David Anglin
2005-11-26 18:31 ` Mark Kettenis
2005-11-27 4:30 ` John David Anglin
2005-11-27 15:10 ` Randolph Chung
2005-11-27 16:52 ` John David Anglin
2005-11-27 17:42 ` 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=43888F83.7090603@tausq.org \
--to=randolph@tausq.org \
--cc=brobecker@adacore.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=gdb@sources.redhat.com \
--cc=mark.kettenis@xs4all.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