From: "Peter S. Mazinger" <ps.m@gmx.net>
To: Daniel Jacobowitz <drow@false.org>
Cc: binutils@sourceware.org
Subject: Re: PATCH for Re: binutils 2.15 / gcc-3.3.5 (3.4.3) produce text relocations on arm
Date: Sat, 19 Mar 2005 01:23:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0503190056300.14102-100000@lnx.bridge.intra> (raw)
In-Reply-To: <20050318220707.GA8643@nevyn.them.org>
On Fri, 18 Mar 2005, Daniel Jacobowitz wrote:
> On Mon, Mar 14, 2005 at 12:44:39PM +0100, Peter S. Mazinger wrote:
> > On Wed, 5 Jan 2005, Peter S. Mazinger wrote:
> >
> > > On Tue, 4 Jan 2005, Daniel Jacobowitz wrote:
> > > > Then could you check whether any of the relocations are actually in the
> > > > text segment?
> > >
> > > How to do that?
>
> Via readelf. readelf -l will show you the offsets and sizes of the
> segments. readelf -Dr will show you the offsets of relocation entries.
> Are any in the text segment?
>
> > >
> > > Could you provide me a patch for the ARM bug you have found (setting
> > > DT_TEXTREL incorrectly)?
>
> Attached.
>
> This is patch 2/2 for today's duplicated-code-in-BFD hatred series. I
> tried to resync with other ports' copies of this code and it proved
> surprisingly twisty, so I took the simple way out. We were creating
> reloc_copied structures with ->count = 0, which are useless and messed
> up the counting algorithm.
>
> Tested arm-linux, binutils and glibc testsuites. Richard or Nick, is
> this patch OK?
tested on uclibc, it "removes" the false DT_TEXTREL from shared libs.
>
> > Nothing changed in the meantime ;-(
> > I have tested binutils-cvs (as of 20050222) and no better.
> >
> > Finally it seems that the DT_TEXTREL entry is coming from assembler
> > sources, C code seems to be linked correctly.
>
> Your assembly sources may be broken (non-PIC) then.
it was, but now it was detectable ;)
>
> > on another note:
> > MAXPAGESIZE=0x8000 (as of bfd/elf.c) for arm, please change that in
> > ld/emulparams/armelf.sh.
>
> Nathan noticed the odd MAXPAGESIZE setting in arm-elf today also. I
> don't know the history.
Please inform me, if you change that (well, I am using it w/ that value
now, the newly added arm stuff also uses it as 0x8000, not as 256)
Thanks Peter
--
Peter S. Mazinger <ps dot m at gmx dot net> ID: 0xA5F059F2
Key fingerprint = 92A4 31E1 56BC 3D5A 2D08 BB6E C389 975E A5F0 59F2
next prev parent reply other threads:[~2005-03-19 0:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0501041617290.874-100000@lnx.bridge.intra>
2005-01-04 16:48 ` Daniel Jacobowitz
2005-01-04 17:17 ` Peter S. Mazinger
2005-01-04 18:35 ` Daniel Jacobowitz
2005-01-05 6:58 ` Peter S. Mazinger
2005-03-14 11:44 ` Peter S. Mazinger
2005-03-18 23:52 ` PATCH for " Daniel Jacobowitz
2005-03-19 1:23 ` Peter S. Mazinger [this message]
2005-04-04 13:52 ` 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=Pine.LNX.4.44.0503190056300.14102-100000@lnx.bridge.intra \
--to=ps.m@gmx.net \
--cc=binutils@sourceware.org \
--cc=drow@false.org \
/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).