Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] pb unwinding from pthread_cond_wait on ppc-linux (RFA?)
Date: Fri, 17 Jun 2005 04:07:00 -0000	[thread overview]
Message-ID: <20050617040635.GJ17013@nevyn.them.org> (raw)
In-Reply-To: <20050209170211.GD18540@adacore.com>

On Wed, Feb 09, 2005 at 12:02:11PM -0500, Joel Brobecker wrote:
> Ping?

You may want to ping at Andrew and Kevin directly about this.

> On Thu, Dec 09, 2004 at 05:00:17PM +0100, Joel Brobecker wrote:
> > > Precisely!  That's what I thought it would be.  It's trying to load lr
> > > with the address of @+16, so that the function can access PIC data
> > > using PC-relative displacement.
> > 
> > Daniel, you never stop to impress me.
> > 
> > > (Does this obsolete the "branch in first three insns" check?  I'm not
> > > sure if there are other possible reasons for that.)
> > 
> > Here is a new patch that implements your suggestion. Indeed, I could
> > then remove the "branch in first three insns" check...

FYI, rethinking this, this is not such a good idea (removing the check,
I mean).  While the check itself is pretty bogus, the comment above
says:
        {                       /* bl foo, 
                                   to save fprs??? */

I know at least Darwin does this.

So maybe the new check should be additional instead of a replacement.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-06-17  4:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08 15:59 Joel Brobecker
2004-12-08 16:32 ` Daniel Jacobowitz
2004-12-08 16:34   ` Joel Brobecker
2004-12-08 16:51     ` Daniel Jacobowitz
2004-12-09 17:23       ` Joel Brobecker
2005-02-09 17:08         ` Joel Brobecker
2005-06-17  4:07           ` Daniel Jacobowitz [this message]
2006-10-11 16:03             ` Joel Brobecker

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=20050617040635.GJ17013@nevyn.them.org \
    --to=drow@false.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sources.redhat.com \
    /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