From: Matt Fischer <mattfischer84@gmail.com>
To: Matt Fischer <mattfischer84@gmail.com>, binutils@sourceware.org
Subject: Re: Load addresses for ELF program headers on ARM
Date: Mon, 11 Oct 2010 15:21:00 -0000 [thread overview]
Message-ID: <AANLkTimCS7WnpcvPkyJz3VDAOCJ0mi4nPk8=h3Qb6t4e@mail.gmail.com> (raw)
In-Reply-To: <20101011144357.GA1024@caradoc.them.org>
On Mon, Oct 11, 2010 at 9:44 AM, Daniel Jacobowitz <dan@codesourcery.com> wrote:
> On Sun, Oct 10, 2010 at 10:38:59PM -0500, Matt Fischer wrote:
>> On Sun, Oct 10, 2010 at 10:29 PM, Alan Modra <amodra@gmail.com> wrote:
>> > On Sun, Oct 10, 2010 at 09:43:27PM -0500, Matt Fischer wrote:
>> >> However, when I do this, it creates one gigantic segment which has
>> >> both sections at their relocation addresses, and zero-fills the 200MB
>> >> or so in between them. It seems like the linker is not correctly
>> >> respecting load addresses when it tries to fit sections into segments.
>> >> Is that something that can be gotten around somehow?
>> >
>> > This is a 2.20 bug. With current mainline you'll get a warning
>> > section `DATA' can't be allocated in segment 0
>> > but ld will place DATA immediately after TEXT in the segment. The
>> > warning is because the VMA for DATA is outside the virtual addresses
>> > covered by your program header. (The warning should probably say
>> > something to that effect rather than "can't be allocated" when the
>> > section *is* allocated there.)
>>
>> Ah, excellent. Ok, so I'll just patch the binaries for now, and then
>> pick up that change once it's available. Dan, any idea when that fix
>> will make its way into Sourcery Lite?
>
> A bit off topic for this list but... If this fix is in
> assign_file_positions_for_load_sections, which I think it is,
> then it will be in our November releases.
Perfect. Thanks to both of you for all your help with this.
--Matt
P.S. Dan--sorry, you're right, I should have queried for the Sourcery
info elsewhere. Thanks for obliging me, though. :)
next prev parent reply other threads:[~2010-10-11 15:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 0:47 Matt Fischer
2010-10-11 1:55 ` Alan Modra
2010-10-11 2:43 ` Matt Fischer
2010-10-11 3:29 ` Alan Modra
2010-10-11 3:39 ` Matt Fischer
2010-10-11 14:44 ` Daniel Jacobowitz
2010-10-11 15:21 ` Matt Fischer [this message]
2011-03-15 15:36 ` Matt Fischer
2011-03-16 4:29 ` Alan Modra
2011-03-17 0:37 ` Matt Fischer
2011-03-17 2:38 ` Alan Modra
2011-03-17 2:56 ` Matt Fischer
2010-10-11 2:50 ` Daniel Jacobowitz
2010-10-11 3:28 ` Matt Fischer
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='AANLkTimCS7WnpcvPkyJz3VDAOCJ0mi4nPk8=h3Qb6t4e@mail.gmail.com' \
--to=mattfischer84@gmail.com \
--cc=binutils@sourceware.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).