public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Richard Earnshaw <Richard.Earnshaw@arm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: David Poole <daveml@mbuf.com>,
	binutils@sources.redhat.com, nickc@redhat.com
Subject: Re: DT_TEXTREL/.dynamic issue with the binutils 2.15 linker on ARM and Linux
Date: Sat, 30 Oct 2004 13:17:00 -0000	[thread overview]
Message-ID: <1099142241.11478.1.camel@pc960.cambridge.arm.com> (raw)
In-Reply-To: <20041029201339.GA10171@nevyn.them.org>

On Fri, 2004-10-29 at 21:13, Daniel Jacobowitz wrote:
> On Tue, Jun 01, 2004 at 10:59:08AM -0600, David Poole wrote:
> > On May 29, 2004, at 12:06 AM, Alan Modra wrote:
> > 
> > >On Fri, May 28, 2004 at 10:56:09AM -0400, Daniel Jacobowitz wrote:
> > >>I don't know why DT_TEXTREL isn't there for this case.  It should be.
> > >
> > >Perhaps because elf32-arm.h doesn't have something like
> > >readonly_dynrelocs as implemented in other backends.
> > 
> > Looking at elf32-i386.c and elf32-s390.c, I copied the 
> > readonly_dynrelocs() and the call in 
> > elf_(i386|s390)_size_dynamic_sections.
> > 
> 
> The patch from the message I'm quoting looks right to me:
>   http://sources.redhat.com/ml/binutils/2004-06/msg00010.html
> 
> However, to apply it, two things need to happen:
>   - An ARM maintainer needs to review it.

I'm happy with this, especially if you are.

>   - Someone needs to decide whether it requires a copyright assignment
>     (my instinct is no, but I don't make these decisions).
> 

I agree, but let's give Nick a couple of days in case he wants to raise
an objection.

R.

  reply	other threads:[~2004-10-30 13:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-28 15:24 David Poole
2004-05-28 15:33 ` Daniel Jacobowitz
2004-05-28 15:54   ` David Poole
2004-05-28 22:58     ` David Poole
2004-05-29  6:21   ` Alan Modra
2004-06-01 16:59     ` David Poole
2004-10-29 20:13       ` Daniel Jacobowitz
2004-10-30 13:17         ` Richard Earnshaw [this message]
2004-11-01 15:14           ` Nick Clifton

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=1099142241.11478.1.camel@pc960.cambridge.arm.com \
    --to=richard.earnshaw@arm.com \
    --cc=binutils@sources.redhat.com \
    --cc=daveml@mbuf.com \
    --cc=drow@false.org \
    --cc=nickc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).