Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: randolph@tausq.org
Cc: dave@hiauly1.hia.nrc.ca, gdb@sources.redhat.com, brobecker@adacore.com
Subject: Re: Register numbers on hppa64
Date: Sun, 27 Nov 2005 17:42:00 -0000	[thread overview]
Message-ID: <200511271652.jARGqJdx016460@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <4389CBA4.6010906@tausq.org> (message from Randolph Chung on Sun, 	27 Nov 2005 23:07:16 +0800)

> Date: Sun, 27 Nov 2005 23:07:16 +0800
> From: Randolph Chung <randolph@tausq.org>
> 
> > If we change the register use in .dwarf_frame, then we are breaking
> > compatibility with previously compiled code.  This isn't a big deal
> > under HP-UX (dwarf debugging was totally broken on hppa64 until a
> > recent assembler fix).  However, there is a fair bit of installed
> > code running linux.  Thus, I would say not change the status quo
> > if the above confusion can be handled.  The actual numbers used for
> > the FP registers are obscure and I doubt many people actually care
> > what they are.  It's only people maintaining the dwarf code that
> > are likely to get confused.  If readelf produced a text rather than
> > numeric representation, then the problem would largely go away.
> 
> If I understand Mark correctly, the suggestion would change the 
> numbering used for dwarf cfi/eh, but not the register numbers emitted 
> for .debug_info, right?

Sorry no.  I propose to use DWARF2_FRAME_REG_OUT() on hppa and hppa32
to change the register numbers for .dwarf_frame to match the ones in
.dwarf_info for ages, and leave .eh_frame alone.  We can't change the
numbers in .eh_frame because that will break binary compatibility for
(C++) exception handling.  It's really silly for .dwarf_info and
.dwarf_frame to use different register numbers.  The fact that on hppa
there is no ABI that defines these register numbers doesn't really
change the argument I made for powerpc.

> FWIW currently on hppa-linux, gdb does not use dwarf cfi for frame 
> unwinding. It's on my list of things to do, but if something need 
> changing in gcc for whatever reason, now is a good time to do it as far 
> as I'm concerned.

Indeed, so the impact of changing the register numbers should be
small.  In addition it doesn't affect the integer registers.  Some
people might have old object modules around that contain the wrong
register numbers, but they'll only affect floating-point registers
which probably don't show up in CFI a lot anyway.

Mark


      parent reply	other threads:[~2005-11-27 16:52 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
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 [this message]

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=200511271652.jARGqJdx016460@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=brobecker@adacore.com \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=gdb@sources.redhat.com \
    --cc=randolph@tausq.org \
    /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