This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Register numbers on hppa64
- From: Mark Kettenis <mark dot kettenis at xs4all dot nl>
- To: dave at hiauly1 dot hia dot nrc dot ca
- Cc: randolph at tausq dot org, gdb at sources dot redhat dot com, brobecker at adacore dot com
- Date: Sat, 26 Nov 2005 19:00:26 +0100 (CET)
- Subject: Re: Register numbers on hppa64
- References: <200511261752.jAQHqPrA004033@hiauly1.hia.nrc.ca>
> Date: Sat, 26 Nov 2005 12:52:25 -0500 (EST)
> From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
>
> > But we have a de-facto ABI since GCC has been using
> > DBX_REGISTER_NUMBER for all non-CFI DWARF2 output. I never noticed
> > DWARF2_FRAME_REG_OUT before, but it seems to implement a suggestion I
> > made in the ppc64 discussion. Now that it's there I really think you
> > should consider using it for hppa/hppa64 too. Something like
> >
> > #define DWARF2_FRAME_REG_OUT(REGNO, FOR_EH) \
> > ((FOR_EH) ? (REGNO) : DBX_REGISTER_NUMBER (REGNO)
> >
> > if pa32-reg.h and pa64-reg.h should be enough.
> >
> > Meanwhile, I should get busy and implement the necessary support in
> > gdb to cope with the fact that .debug_frame has a different encoding
> > than .eh_frame.
>
> Let me understand, are you saying that .debug_frame has a mix
> of gcc and dbx register numbers at present (i.e., it contains
> both cfi and non-cfi data)? If that's the case and it's hard
> for gdb to tell the difference, then I agree that we should
> make the above change.
No what I'm saying is that .dwarf_frame uses different register
numbers than .debug_info and other .debug_xxx sections. This is
awkward and confusing because the same DWARF operations that refer to
register numbers are used in both sections but suddenly have a
different meaning.
Mark