This is the mail archive of the
mailing list for the binutils project.
Re: [Bug ld/12565] NOLOAD sections empty
- From: Dave Murphy <davem at devkitpro dot org>
- To: Nick Clifton <nickc at redhat dot com>
- Cc: "hjl.tools at gmail dot com" <sourceware-bugzilla at sourceware dot org>, Alan Modra <amodra at gmail dot com>, binutils <binutils at sourceware dot org>
- Date: Thu, 30 Jun 2011 16:39:44 +0100
- Subject: Re: [Bug ld/12565] NOLOAD sections empty
- References: <firstname.lastname@example.org/bugzilla/> <bug-12565-70-H4yGNZZKA2@http.sourceware.org/bugzilla/> <4E0C8A37.email@example.com>
On Thu, Jun 30, 2011 at 3:37 PM, Nick Clifton <firstname.lastname@example.org> wrote:
> Hi H.J., Hi Alan,
> I have been looking at PR 12565, and I have to say that I do not understand the linker's behaviour for NOLOAD sections on ELF based targets. ?What is the point of having a section that cannot be loaded and that does not have any contents ?
> Also, as far as I can see, this behaviour is not documented anywhere. Do you know of any applications that rely upon this feature ?
I thought it was for bss segments.
I've been using that flag to allow me to overly bss sections on top of
other sections that are copied to other memory locations at runtime.
If I didn't use NOLOAD then the linker would complain about