aboutsummaryrefslogtreecommitdiff
path: root/ld/ld.texinfo
diff options
context:
space:
mode:
authorNick Clifton <nickc@redhat.com>2000-04-25 00:27:24 +0000
committerNick Clifton <nickc@redhat.com>2000-04-25 00:27:24 +0000
commit2b5fc1f5d0a3d5063c7e4a75c70eab38386ad84d (patch)
tree45218ccf58bf23cdeaceb7b9634639ae3eacf42f /ld/ld.texinfo
parentadcf07e61499b211183ca7135933a026764d4561 (diff)
downloadfsf-binutils-gdb-2b5fc1f5d0a3d5063c7e4a75c70eab38386ad84d.zip
fsf-binutils-gdb-2b5fc1f5d0a3d5063c7e4a75c70eab38386ad84d.tar.gz
fsf-binutils-gdb-2b5fc1f5d0a3d5063c7e4a75c70eab38386ad84d.tar.bz2
Note that output section data commands can only appear inside output section
descriptions and not between them.
Diffstat (limited to 'ld/ld.texinfo')
-rw-r--r--ld/ld.texinfo10
1 files changed, 10 insertions, 0 deletions
diff --git a/ld/ld.texinfo b/ld/ld.texinfo
index c9d0fc6..e8c11d9 100644
--- a/ld/ld.texinfo
+++ b/ld/ld.texinfo
@@ -2486,6 +2486,16 @@ When the object file format does not have an explicit endianness, as is
true of, for example, S-records, the value will be stored in the
endianness of the first input object file.
+Note - these commands only work inside a section description and not
+between them, so the following will produce an error from the linker:
+@smallexample
+SECTIONS @{@ .text : @{@ *(.text) @}@ LONG(1) .data : @{@ *(.data) @}@ @}@
+@end smallexample
+whereas this will work:
+@smallexample
+SECTIONS @{@ .text : @{@ *(.text) ; LONG(1) @}@ .data : @{@ *(.data) @}@ @}@
+@end smallexample
+
@kindex FILL(@var{expression})
@cindex holes, filling
@cindex unspecified memory