Fix examples of the use of the linker script TYPE keyword

This commit is contained in:
Nick Clifton
2024-12-20 11:00:15 +00:00
parent 45b4f0499c
commit 14848fc2b2

View File

@@ -5970,19 +5970,19 @@ special requirements of the section type are met.
Note - the TYPE only is used if some or all of the contents of the
section do not have an implicit type of their own. So for example:
@smallexample
.foo . TYPE = SHT_PROGBITS @{ *(.bar) @}
.foo . (TYPE = SHT_PROGBITS) : @{ *(.bar) @}
@end smallexample
will set the type of section @samp{.foo} to the type of the section
@samp{.bar} in the input files, which may not be the SHT_PROGBITS
type. Whereas:
@smallexample
.foo . TYPE = SHT_PROGBITS @{ BYTE(1) @}
.foo . (TYPE = SHT_PROGBITS) : @{ BYTE(1) @}
@end smallexample
will set the type of @samp{.foo} to SHT_PROGBBITS. If it is necessary
to override the type of incoming sections and force the output section
type then an extra piece of untyped data will be needed:
@smallexample
.foo . TYPE = SHT_PROGBITS @{ BYTE(1); *(.bar) @}
.foo . (TYPE = SHT_PROGBITS) : @{ BYTE(1); *(.bar) @}
@end smallexample
@item READONLY ( TYPE = @var{type} )