From: Geoff Keating <geoffk@desire.geoffk.org>
To: cagney@gnu.org
Cc: kettenis@chello.nl, dje@watson.ibm.com, gcc@gcc.gnu.org,
gdb-patches@sources.redhat.com, Ulrich.Weigand@de.ibm.com
Subject: Re: Incorrect DWARF-2 register numbers on PPC64?
Date: Fri, 02 Jan 2004 23:18:00 -0000 [thread overview]
Message-ID: <200401022317.i02NHQBR001191@desire.geoffk.org> (raw)
In-Reply-To: <3FF5A069.1040306@gnu.org> (message from Andrew Cagney on Fri, 02 Jan 2004 11:46:33 -0500)
> Date: Fri, 02 Jan 2004 11:46:33 -0500
> From: Andrew Cagney <cagney@gnu.org>
> I'd ignore GDB here. I think GCC, for the 64-bit SvR4 PPC ABI, should
> use the correct numbers. If that means GDB tweaks, so be it.
I agree with this. I'd even agree with changing the 32-bit numbering
to be more correct. As I said elsewhere, there may be trouble with
exception handling, but even then I'd support changing the numbers of
registers that aren't caller-saved, to make GCC as correct as
possible.
--
- Geoffrey Keating <geoffk@geoffk.org>
next prev parent reply other threads:[~2004-01-02 23:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OFEA5CA921.302AEEB5-ON41256E00.005FB141@de.ibm.com>
2003-12-18 22:58 ` David Edelsohn
2003-12-20 15:27 ` Mark Kettenis
2004-01-02 16:46 ` Andrew Cagney
2004-01-02 23:18 ` Geoff Keating [this message]
2004-01-06 15:27 ` Alan Modra
[not found] ` <amodra@bigpond.net.au>
2004-01-06 16:02 ` David Edelsohn
2004-01-06 18:07 ` Geoff Keating
2004-01-06 18:10 ` David Edelsohn
2004-01-06 22:05 ` Geoff Keating
2004-01-06 22:09 ` David Edelsohn
2004-01-06 22:34 ` Geoff Keating
2004-01-07 0:27 ` Alan Modra
2004-01-07 17:43 ` Mark Kettenis
2004-01-07 22:29 ` Alan Modra
2004-01-07 23:36 ` Andrew Cagney
2004-01-08 0:48 ` Alan Modra
2004-01-08 5:02 ` Geoff Keating
2004-01-09 2:34 ` Alan Modra
2004-01-09 2:49 ` Alan Modra
2004-01-09 6:39 ` Alan Modra
2004-01-09 15:16 ` 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=200401022317.i02NHQBR001191@desire.geoffk.org \
--to=geoffk@desire.geoffk.org \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=cagney@gnu.org \
--cc=dje@watson.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.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