From: "H.J. Lu" <hjl.tools@gmail.com>
To: Andreas Schwab <schwab@redhat.com>,
"H.J. Lu" <hjl.tools@gmail.com>,
David Stubbs <stubbs@icerasemi.com>,
binutils@sourceware.org
Cc: Alan Modra <amodra@gmail.com>
Subject: Re: VMA section overlap warnings for overlays
Date: Thu, 24 Feb 2011 23:49:00 -0000 [thread overview]
Message-ID: <AANLkTinZVnBqun1qxJHgWiFfYkHWF=XpxGFz2aX65v8B@mail.gmail.com> (raw)
In-Reply-To: <20100720141031.GI19525@bubble.grove.modra.org>
On Tue, Jul 20, 2010 at 7:10 AM, Alan Modra <amodra@gmail.com> wrote:
> This removes all the special treatment for zero size sections when
> using ELF_SECTION_IN_SEGMENT in elf.c, and makes readelf display
> section to segment mapping for zero size sections. I chose to not
> include a zero size section in readelf's mapping if the section was at
> the end of a segment. eg. if the segment covers 0x1000 to 0x1fff,
> then a zero sized section located at 0x2000 is not shown as part of
> the segment. That seems reasonable to me, but I'm open to
> suggestions. I'll note that omitting sections like this in elf.c, ie.
> using ELF_SECTION_IN_SEGMENT_STRICT there, causes testsuite failures
> on x86. A zero length .got.plt sometimes ends up as the last section
> mapped to a load segment.
>
> include/elf/
> * internal.h (ELF_TBSS_SPECIAL): New macro, extracted from..
> (ELF_SECTION_SIZE): ..here.
> (ELF_SECTION_IN_SEGMENT_1): Add "strict" arg.
> (ELF_SECTION_IN_SEGMENT_STRICT): New macro.
> bfd/
> * elf.c (assign_file_positions_for_load_sections): Check that
> zero size sections are allocated in segments too.
> (assign_file_positions_for_non_load_sections): Warn if zero
> size alloc sections are found here.
> (copy_elf_program_header): Don't drop zero size sections from
> segment map.
> (copy_private_bfd_data): Check for changes in zero size sections.
> binutils/
> * readelf.c (process_program_headers): Don't ignore all zero size
> sections.
> ld/testsuite/
> * ld-powerpc/tlsexe.r: Update.
> * ld-powerpc/tlsexetoc.r: Update.
> * ld-powerpc/tlsso.r: Update.
> * ld-powerpc/tlstocso.r: Update.
>
This may have caused:
http://sourceware.org/bugzilla/show_bug.cgi?id=12516
--
H.J.
next prev parent reply other threads:[~2011-02-24 23:49 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 13:29 David Stubbs
2010-04-21 8:25 ` Alan Modra
2010-04-21 14:44 ` David Stubbs
2010-04-22 1:11 ` Alan Modra
2010-04-22 1:53 ` Alan Modra
2010-04-22 12:39 ` David Stubbs
2010-04-24 2:18 ` Alan Modra
2010-05-07 16:14 ` David Stubbs
2010-05-08 11:49 ` Alan Modra
2010-05-12 13:19 ` David Stubbs
2010-05-13 3:37 ` Alan Modra
2010-07-15 8:11 ` Andreas Schwab
2010-07-15 13:10 ` Alan Modra
2010-07-15 13:46 ` Andreas Schwab
2010-07-15 13:53 ` H.J. Lu
2010-07-15 14:12 ` Andreas Schwab
2010-07-15 14:17 ` H.J. Lu
2010-07-15 14:18 ` Alan Modra
2010-07-15 14:26 ` H.J. Lu
2010-07-15 14:36 ` Andreas Schwab
2010-07-15 19:09 ` H.J. Lu
2010-07-16 7:39 ` Andreas Schwab
2010-07-16 10:04 ` Alan Modra
2010-07-19 12:43 ` Andreas Schwab
2010-07-20 5:45 ` Alan Modra
2010-07-20 14:11 ` Alan Modra
2011-02-24 23:49 ` H.J. Lu [this message]
2011-02-25 7:49 ` Alan Modra
2011-02-25 10:17 ` Andreas Schwab
2011-02-25 12:30 ` H.J. Lu
2011-02-25 15:55 ` H.J. Lu
2011-02-25 16:23 ` Andreas Schwab
2011-02-25 16:34 ` H.J. Lu
2010-08-28 1:02 ` H.J. Lu
2010-08-28 11:00 ` Alan Modra
2010-08-28 13:39 ` Alan Modra
2010-08-28 17:25 ` H.J. Lu
2010-08-30 4:46 ` Alan Modra
2010-08-30 5:11 ` H.J. Lu
2010-08-30 6:30 ` Alan Modra
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='AANLkTinZVnBqun1qxJHgWiFfYkHWF=XpxGFz2aX65v8B@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=schwab@redhat.com \
--cc=stubbs@icerasemi.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).