public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
	 gdb@sources.redhat.com,   brobecker@adacore.com
Subject: Re: Register numbers on hppa64
Date: Sun, 27 Nov 2005 15:10:00 -0000	[thread overview]
Message-ID: <4389CBA4.6010906@tausq.org> (raw)
In-Reply-To: <200511261849.jAQInvcq019702@hiauly1.hia.nrc.ca>

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

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.

randolph

  reply	other threads:[~2005-11-27 15:07 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 [this message]
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=4389CBA4.6010906@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).