From: Alan Modra <amodra@gmail.com>
To: David Stubbs <stubbs@IceraSemi.com>
Cc: binutils@sourceware.org, sdkteam-gnu <sdkteam-gnu@IceraSemi.com>
Subject: Re: VMA section overlap warnings for overlays
Date: Thu, 13 May 2010 03:37:00 -0000 [thread overview]
Message-ID: <20100513033742.GH5443@bubble.grove.modra.org> (raw)
In-Reply-To: <4D60B0700D1DB54A8C0C6E9BE69163700ED69E1A@EXCHANGEVS.IceraSemi.local>
On Wed, May 12, 2010 at 02:19:24PM +0100, David Stubbs wrote:
> I have however found another potential problem with strip. Here's the
> test:
[snip]
> brsbs01 1>strip test.exe
> BFD: stHVOxcK: section .overlay1.bss lma 0x1021 overlaps previous
> sections
> BFD: stHVOxcK: section .overlay2.bss lma 0x1021 overlaps previous
> sections
This is caused by the heuristics we use to set LMA for SHT_NOBITS
sections (bfd/elf.c:984). I don't think we can make any changes here
though: sh_offset isn't really valid for a SHT_NOBITS section.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2010-05-13 3:37 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 [this message]
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
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=20100513033742.GH5443@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=sdkteam-gnu@IceraSemi.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).