From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: schwab@suse.de, gdb-patches@sourceware.org
Subject: Re: Use DWARF CFI frame unwinder on powerpc
Date: Mon, 15 May 2006 19:10:00 -0000 [thread overview]
Message-ID: <200605151906.k4FJ6ERN027161@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20060515161213.GE28924@nevyn.them.org> (message from Daniel Jacobowitz on Mon, 15 May 2006 12:12:13 -0400)
> Date: Mon, 15 May 2006 12:12:13 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> Hi Andreas,
>
> I know we tried to do this once before, and ran into hiccups based on
> the GCC numbering being inconsistent. Do we know which versions of GCC
> this is likely to work with, and which are likely to make it fall down
> horribly? I recall that GPRs were OK, but the numbering for LR was
> ambiguous.
>
> It might have been this:
> 2004-01-21 Alan Modra <amodra@bigpond.net.au>
>
> * config/rs6000/sysv4.h (DWARF2_FRAME_REG_OUT): Define.
> * dwarf2out.c (output_cfi): Map regs using DWARF2_FRAME_REG_OUT.
> * doc/tm.texi (DWARF_FRAME_REGNUM, DWARF2_FRAME_REG_OUT): Document.
>
> Yep, here's Mark K. and Alan discussing it:
> http://gcc.gnu.org/ml/gcc/2004-01/msg00025.html
>
> I'm worried that since we don't currently use the "this is the unwind
> column" to indicate where lr lives in the table, although we could,
> we'll break on pre-3.4-ish(?) binaries.
Just verified that Andreas' patch breaks GDB on OpenBSD/macppc 3.9
which uses GCC 3.3.5 :(. I'm afraid this means we can't
unconditionally enable the dwarf2 unwinder on all powerpc targets.
Selectively enabling them on platforms that are unlikely to have ever
used GCC versions before 3.4 should be fine. I think all 64-bit
powerpc targets should be fine.
I'll have a look at what's needed to make things work for the old
unwind information.
Mark
next prev parent reply other threads:[~2006-05-15 19:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 14:16 Andreas Schwab
2006-05-09 17:17 ` PAUL GILLIAM
2006-05-09 17:23 ` Daniel Jacobowitz
2006-05-09 22:26 ` PAUL GILLIAM
2006-05-09 17:46 ` Andreas Schwab
2006-05-09 18:01 ` David S. Miller
2006-05-09 18:39 ` Daniel Jacobowitz
2006-05-09 21:07 ` David S. Miller
2006-05-15 16:46 ` Daniel Jacobowitz
2006-05-15 19:10 ` Mark Kettenis [this message]
2006-05-15 20:43 ` Daniel Jacobowitz
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=200605151906.k4FJ6ERN027161@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=schwab@suse.de \
/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