public inbox for prelink@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Catherine Moore <clm@codesourcery.com>,
	prelink@sourceware.org, 	rdsandiford@googlemail.com
Subject: Re: [patch] Add support for new mips relocs
Date: Wed, 03 Dec 2008 20:03:00 -0000	[thread overview]
Message-ID: <20081203200226.GA28907@caradoc.them.org> (raw)
In-Reply-To: <87r64pcapp.fsf@firetop.home>

Catherine, please preserve attribution when you can; I wrote all
this.  Thanks.

On Wed, Dec 03, 2008 at 07:36:34PM +0000, Richard Sandiford wrote:
> I'm probably missing something, sorry, but how does the patch handle
> the property mentioned in the original comment?  Relocations must never
> resolve to another object's (traditional) lazy-binding stub.

This does happen, but the code that does it is far away: in this case,
in glibc.  The dynamic loader will output which object it bound the
relocation to, and it will be one that contains a definition rather
than a lazy binding stub.

As you may remember, we also have cross prelink support in our local
tree (I'm willing to take a stab at submitting this if Jakub is
interested).  That has basically a copy of the glibc resolver in it.
And that's where the STO_MIPS_PLT check lives for cross operation.

-- 
Daniel Jacobowitz
CodeSourcery

  reply	other threads:[~2008-12-03 20:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-03 18:46 Catherine Moore
2008-12-03 19:37 ` Richard Sandiford
2008-12-03 20:03   ` Daniel Jacobowitz [this message]
2008-12-03 20:12     ` Richard Sandiford
2008-12-03 20:29       ` Daniel Jacobowitz
2008-12-16 16:27         ` Daniel Jacobowitz
2009-01-12 17:28           ` 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=20081203200226.GA28907@caradoc.them.org \
    --to=drow@false.org \
    --cc=clm@codesourcery.com \
    --cc=prelink@sourceware.org \
    --cc=rdsandiford@googlemail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).