From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: jan.kratochvil@redhat.com, gdb-patches@sourceware.org,
schwab@suse.de, brobecker@adacore.com
Subject: Re: [PATCH] Fix PPC non-CFI + CFI unwinding (incomplete in HEAD)
Date: Sat, 13 Jan 2007 16:40:00 -0000 [thread overview]
Message-ID: <20070113164028.GA29436@nevyn.them.org> (raw)
In-Reply-To: <200701131631.l0DGVW3W029896@brahms.sibelius.xs4all.nl>
On Sat, Jan 13, 2007 at 05:31:32PM +0100, Mark Kettenis wrote:
> > Date: Sat, 13 Jan 2007 11:04:20 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> >
> > On Sat, Jan 13, 2007 at 10:30:52AM +0100, Jan Kratochvil wrote:
> > > 2007-01-01 Jan Kratochvil <jan.kratochvil@redhat.com>
> > >
> > > * rs6000-tdep.c (skip_prologue): Handle bl->brlr used by PIC code.
> >
> > IIRC Joel was working on a patch for this case too. I'd been hoping one of
> > our PPC experts would look at it...
>
> I've completely lost track of the various powerpc prologue scanner
> fixes floating around. Is this patch supposed to fix the same problem
> as the test below exposes?
No, I don't think so - it's about the blrl at the front of the GOT in
PIC code.
I was thinking of this:
http://sourceware.org/ml/gdb-patches/2004-12/msg00249.html
http://sourceware.org/ml/gdb-patches/2005-06/msg00242.html
I think someone needs to combine Joel's and Jan's patches. Joel's is
nicer in that it uses branch_dest and the right mask for blrl; Jan's
is nicer in that it checks whether lr was saved or is now lost.
> + " stwu %r1,-32(%r1)\n"
> + " lis %r9,-16342\n"
> + " lis %r11,-16342\n"
> + " mflr %r0\n"
> + " addi %r11,%r11,3776\n"
> + " stmw %r27,12(%r1)\n"
> + " addi %r31,%r9,3152\n"
> + " cmplw %cr7,%r31,%r11\n"
> + " stw %r0,36(%r1)\n"
> + " mr %r30,%r3\n"
> + " bl optimized_1_marker\n"
> + " lwz %r0,36(%r1)\n"
> + " lmw %r27,12(%r1)\n"
> + " addi %r1,%r1,32\n"
> " blr");
Looks like a different problem to me :-(
By the way, Mark, did you see this message?
http://sourceware.org/ml/gdb-patches/2006-10/msg00233.html
I'd still like to fix that problem one way or another. If you haven't
got time to look at it, I was considering setting up a virtual machine
for the appropriate version of OpenBSD - it would be fearsomely slow,
but I'm sure it would work.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-01-13 16:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-13 9:31 Jan Kratochvil
2007-01-13 16:04 ` Daniel Jacobowitz
2007-01-13 16:32 ` Mark Kettenis
2007-01-13 16:40 ` Daniel Jacobowitz [this message]
2007-01-14 21:34 ` Jan Kratochvil
2007-01-20 19:57 ` Daniel Jacobowitz
2007-01-21 10:41 ` Mark Kettenis
2007-01-21 21:47 ` Jan Kratochvil
2007-02-08 14:24 ` 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=20070113164028.GA29436@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=mark.kettenis@xs4all.nl \
--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