From: Matt Fischer <mattfischer84@gmail.com>
To: Matt Fischer <mattfischer84@gmail.com>, binutils@sourceware.org
Cc: Alan Modra <amodra@gmail.com>
Subject: Re: Load addresses for ELF program headers on ARM
Date: Thu, 17 Mar 2011 00:37:00 -0000 [thread overview]
Message-ID: <AANLkTi=gyOPhyjHTBVyvxy54sQ0bpjXsqn+r8QS9-0L7@mail.gmail.com> (raw)
In-Reply-To: <20110316042923.GQ6275@bubble.grove.modra.org>
That does seem to fix the problem. It looks like that change simply
disables the VMA check on the section, which makes sense because in
this model the section's VMA won't be inside of the segment anymore.
Given that the code inside this block looks like it can correctly deal
with a segment that contains noncontiguous VMA's, I'm assuming this
change is ok to submit as an actual patch, correct? If so, I'd be
happy to write it up and submit it, if you'd like.
--Matt
On Tue, Mar 15, 2011 at 11:29 PM, Alan Modra <amodra@gmail.com> wrote:
> You might like to change the ELF_SECTION_IN_SEGMENT (hdr, phdr) in
> elf.c:_bfd_elf_make_section_from_shdr to
> ELF_SECTION_IN_SEGMENT_1 (hdr, phdr, 0, 0), and see what happens.
>
> --
> Alan Modra
> Australia Development Lab, IBM
>
next prev parent reply other threads:[~2011-03-17 0:37 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
2011-03-15 15:36 ` Matt Fischer
2011-03-16 4:29 ` Alan Modra
2011-03-17 0:37 ` Matt Fischer [this message]
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='AANLkTi=gyOPhyjHTBVyvxy54sQ0bpjXsqn+r8QS9-0L7@mail.gmail.com' \
--to=mattfischer84@gmail.com \
--cc=amodra@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).