public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "Peter S. Mazinger" <ps.m@gmx.net>
Cc: binutils@sourceware.org
Subject: Re: elf32-arm.c corrections
Date: Sun, 20 Mar 2005 19:45:00 -0000	[thread overview]
Message-ID: <20050320153916.GA26320@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0503201020200.30868-100000@lnx.bridge.intra>

On Sun, Mar 20, 2005 at 10:26:12AM +0100, Peter S. Mazinger wrote:
> On Sat, 19 Mar 2005, Daniel Jacobowitz wrote:
> 
> > On Sun, Mar 20, 2005 at 02:15:24AM +0100, Peter S. Mazinger wrote:
> > > Hello!
> > > 
> > > add_dynamic_entry: changes !info->shared to info->executable (PIE)
> > > corrects typo, and syncs up with other archs (some others could do the 
> > > same). For !relocs the hole part would be omitted, probably some speed gain.
> > 
> > Um, why are disabling the setting of DT_TEXTREL for shared libraries?
> 
> The 1 line removal is because none of the archs has that.
> The i386 implementation has everything within if (relocs), the other 
> archs have it outside, but DT_TEXTREL is only valid for if (relocs), so we 
> would omit that part gaining some speed

Ah, not enough context in the diff.  Makes sense.

> > > Should the other patch (*3) for allocate_dynrelocs be applied (as done for 
> > > ppc32)?
> > 
> > Probably.
> 
> I am asking it, because no other arch has that, only ppc32, so there must 
> be some other solution to that as well.
> 
> > 
> > > Why is ELIMINATE_COPY_RELOCS not used for arm?
> > 
> > Because no one implemented it.
> 
> Would the implementation make the binaries smaller?

Not appreciably.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

  reply	other threads:[~2005-03-20 15:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-20  6:08 Peter S. Mazinger
2005-03-20 13:19 ` Daniel Jacobowitz
2005-03-20 15:39   ` Peter S. Mazinger
2005-03-20 19:45     ` Daniel Jacobowitz [this message]
2005-03-27 22:57       ` Peter S. Mazinger
2005-03-27 23:56         ` Daniel Jacobowitz
2005-03-28  1:58           ` Peter S. Mazinger
2005-03-29 22:05             ` Nick Clifton
2005-04-04 13:45 ` Richard Earnshaw
2005-04-04 14:27   ` Peter S. Mazinger
2005-04-04 14:41     ` Richard Earnshaw

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=20050320153916.GA26320@nevyn.them.org \
    --to=drow@false.org \
    --cc=binutils@sourceware.org \
    --cc=ps.m@gmx.net \
    /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).