https://sourceware.org/bugzilla/show_bug.cgi?id=12565
Christian Bruel chrbr at gcc dot gnu.org changed:
What|Removed |Added
CC||chrbr at
http://sourceware.org/bugzilla/show_bug.cgi?id=12565
--- Comment #15 from Jonathan Larmour jifl-bugzilla at jifvik dot org
2011-07-01 08:57:41 UTC ---
(In reply to comment #14)
I spent quite a lot of time wrestling with NOLOAD before
http://sourceware.org/ml/binutils/2010-09/msg00245.html.
Hi Jifl,
Also, as far as I can see, this behaviour is not documented anywhere.
It is documented in ld.texinfo in the 'Output Section Type' node:
@item NOLOAD
The section should be marked as not loadable, so that it will not be
loaded into memory when the program is run.
But that does not
http://sourceware.org/bugzilla/show_bug.cgi?id=12565
--- Comment #16 from Nick Clifton nickc at redhat dot com 2011-07-01 12:45:37
UTC ---
Hi Jifl,
Also, as far as I can see, this behaviour is not documented anywhere.
It is documented in ld.texinfo in the 'Output Section Type' node:
@item
Hi H.J.
Also, as far as I can see, this behaviour is not documented anywhere.
Do you know of any applications that rely upon this feature ?
NOLOAD means don't load into memory, which maps to NOBITS.
Otherwise, it will be loaded into memory.
OK, I now get that NOLOAD is effectively a marker
http://sourceware.org/bugzilla/show_bug.cgi?id=12565
--- Comment #17 from Nick Clifton nickc at redhat dot com 2011-07-01 12:52:14
UTC ---
Hi H.J.
Also, as far as I can see, this behaviour is not documented anywhere.
Do you know of any applications that rely upon this feature ?
NOLOAD means
http://sourceware.org/bugzilla/show_bug.cgi?id=12565
--- Comment #19 from Nick Clifton nickc at redhat dot com 2011-07-01 13:14:34
UTC ---
Hi Doug,
The ARM linux kernel also uses NOLOAD.
Do you know if this entirely for .bss style sections, or maybe for
establishing a region of memory mapped
Hi Ian,
If you look in the libgloss linker scripts you will see a bunch of uses
of NOLOAD.
I'm not sure whether any of them are really necessary, but they are
certainly there.
Apart from a few .bss sections and one target which uses them to get the
addresses of its hardware I/O ports, all
http://sourceware.org/bugzilla/show_bug.cgi?id=12565
--- Comment #18 from Nick Clifton nickc at redhat dot com 2011-07-01 13:10:20
UTC ---
Hi Ian,
If you look in the libgloss linker scripts you will see a bunch of uses
of NOLOAD.
I'm not sure whether any of them are really necessary, but
http://sourceware.org/bugzilla/show_bug.cgi?id=12565
--- Comment #20 from Jonathan Larmour jifl-bugzilla at jifvik dot org
2011-07-01 23:22:43 UTC ---
Hi Nicl,
(In reply to comment #16)
It is documented in ld.texinfo in the 'Output Section Type' node:
@item NOLOAD
The section should be
http://sourceware.org/bugzilla/show_bug.cgi?id=12565
--- Comment #8 from davem at devkitpro dot org 2011-06-30 15:36:49 UTC ---
On Thu, Jun 30, 2011 at 3:37 PM, Nick Clifton ni...@redhat.com wrote:
Hi H.J., Hi Alan,
I have been looking at PR 12565, and I have to say that I do not understand
http://sourceware.org/bugzilla/show_bug.cgi?id=12565
--- Comment #7 from H.J. Lu hjl.tools at gmail dot com 2011-06-30 14:47:49
UTC ---
(In reply to comment #6)
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
http://sourceware.org/bugzilla/show_bug.cgi?id=12565
--- Comment #9 from davem at devkitpro dot org 2011-06-30 15:40:01 UTC ---
On Thu, Jun 30, 2011 at 3:37 PM, Nick Clifton ni...@redhat.com wrote:
Hi H.J., Hi Alan,
I have been looking at PR 12565, and I have to say that I do not understand
http://sourceware.org/bugzilla/show_bug.cgi?id=12565
--- Comment #10 from iant at google dot com 2011-06-30 16:39:39 UTC ---
Nick Clifton ni...@redhat.com writes:
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
http://sourceware.org/bugzilla/show_bug.cgi?id=12565
--- Comment #11 from Doug Kwan dougkwan at google dot com 2011-06-30 18:24:45
UTC ---
The ARM linux kernel also uses NOLOAD. I added support for that in
gold to link the kernel.
-Doug
On Thu, Jun 30, 2011 at 9:07 AM, Ian Lance Taylor
http://sourceware.org/bugzilla/show_bug.cgi?id=12565
--- Comment #12 from Jonathan Larmour jifl-bugzilla at jifvik dot org
2011-06-30 21:24:57 UTC ---
(In reply to comment #6)
I have been looking at PR 12565, and I have to say that I do not
understand the linker's behaviour for NOLOAD
http://sourceware.org/bugzilla/show_bug.cgi?id=12565
Alan Modra amodra at gmail dot com changed:
What|Removed |Added
CC||amodra at gmail
http://sourceware.org/bugzilla/show_bug.cgi?id=12565
--- Comment #14 from Alan Modra amodra at gmail dot com 2011-07-01 00:03:38
UTC ---
On Thu, Jun 30, 2011 at 03:37:43PM +0100, Nick Clifton wrote:
Hi H.J., Hi Alan,
I have been looking at PR 12565, and I have to say that I do not
http://sourceware.org/bugzilla/show_bug.cgi?id=12565
--- Comment #2 from Jonathan Larmour jifl-bugzilla at jifvik dot org
2011-03-15 19:52:27 UTC ---
Yes here's a definite way to reproduce. I can definitely confirm it's
platform-independent in fact as I've reproduced it with native Linux. Here
http://sourceware.org/bugzilla/show_bug.cgi?id=12565
--- Comment #4 from Jonathan Larmour jifl-bugzilla at jifvik dot org
2011-03-15 22:37:58 UTC ---
(In reply to comment #3)
Created attachment 5312 [details]
A patch
Although the linker script is bad, this patch help it.
Sorry, I was
http://sourceware.org/bugzilla/show_bug.cgi?id=12565
--- Comment #5 from Jonathan Larmour jifl-bugzilla at jifvik dot org
2011-03-15 22:39:05 UTC ---
(In reply to comment #4)
And edit script.ld to include:
.foobar0 : { *(.foobar) }
and you see useful data. All well and good.
To
http://sourceware.org/bugzilla/show_bug.cgi?id=12565
H.J. Lu hjl.tools at gmail dot com changed:
What|Removed |Added
Status|NEW |WAITING
---
http://sourceware.org/bugzilla/show_bug.cgi?id=12565
H.J. Lu hjl.tools at gmail dot com changed:
What|Removed |Added
CC||hjl.tools at gmail
23 matches
Mail list logo
