[RFC PATCH] gas: correct .bss documentation for non-ELF
Jan Beulich
jbeulich@suse.com
Fri Nov 24 13:16:52 GMT 2023
Only ELF permits the specification of a subsection.
---
Except for H8 this doesn't look to have any effect, because all.texi
blindly enables various object formats. Yet still the documentation ends
up wrong for non-ELF targets.
--- a/gas/doc/as.texi
+++ b/gas/doc/as.texi
@@ -4456,7 +4456,12 @@ Some machine configurations provide addi
* Asciz:: @code{.asciz "@var{string}"}@dots{}
* Attach_to_group:: @code{.attach_to_group @var{name}}
* Balign:: @code{.balign [@var{abs-expr}[, @var{abs-expr}]]}
+@ifset ELF
* Bss:: @code{.bss @var{subsection}}
+@end ifset
+@ifclear ELF
+* Bss:: @code{.bss}
+@end ifclear
* Bundle directives:: @code{.bundle_align_mode @var{abs-expr}}, etc
* Byte:: @code{.byte @var{expressions}}
* CFI directives:: @code{.cfi_startproc [simple]}, @code{.cfi_endproc}, etc.
@@ -4801,8 +4806,14 @@ filled in with the value 0x368d (the exa
the endianness of the processor). If it skips 1 or 3 bytes, the fill value is
undefined.
+@ifset ELF
@node Bss
@section @code{.bss @var{subsection}}
+@end ifset
+@ifclear ELF
+@node Bss
+@section @code{.bss}
+@end ifclear
@cindex @code{bss} directive
@code{.bss} tells @command{@value{AS}} to assemble the following statements
More information about the Binutils
mailing list