From: Mark Kettenis <kettenis@chello.nl>
To: amodra@bigpond.net.au
Cc: geoffk@desire.geoffk.org, cagney@gnu.org,
gcc-patches@gcc.gnu.org, dje@watson.ibm.com,
gdb-patches@sources.redhat.com, Ulrich.Weigand@de.ibm.com
Subject: Re: Incorrect DWARF-2 register numbers on PPC64?
Date: Fri, 09 Jan 2004 15:16:00 -0000 [thread overview]
Message-ID: <200401091515.i09FFTBh000400@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <20040109023442.GF2969@bubble.modra.org> (message from Alan Modra on Fri, 9 Jan 2004 13:04:42 +1030)
Date: Fri, 9 Jan 2004 13:04:42 +1030
From: Alan Modra <amodra@bigpond.net.au>
On Wed, Jan 07, 2004 at 09:01:31PM -0800, Geoff Keating wrote:
> That will also mean that executables built with a new version of GCC won't
> run on operating systems with an old libgcc. For Darwin, because of
> historical mistakes involving non-shared libgcc, it will make life
> very difficult.
I hadn't thought of that. This means we are stuck with the current
.eh_frame register numbering.
I was afraid of that :-(.
It should be possible to fix .debug_frame with something like the
following totally untested patch. I'm throwing it out to the list
now for comment.
That way we can hope that GCC's .dwarf_frame will be compatible with
DWARF CFI generated by other compilers, which would be a great win I
think. GDB doesn't support different register encodings for .eh_frame
and .dwarf_frame yet, but that should be fixable; we can distinguish
between the two.
Mark
prev parent reply other threads:[~2004-01-09 15:16 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
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 [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=200401091515.i09FFTBh000400@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=amodra@bigpond.net.au \
--cc=cagney@gnu.org \
--cc=dje@watson.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=geoffk@desire.geoffk.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