This is PR36298.
(COPY), (INFO), (OVERLAY) all have the same effect:
section should be marked as non-allocatable.
(https://www.eecs.umich.edu/courses/eecs373/readings/Linker.pdf,
3.6.8.1 Output Section Type)
Differential D43071
[ELF] - Support COPY, INFO, OVERLAY output sections attributes. grimar on Feb 8 2018, 7:04 AM. Authored by
Details This is PR36298. (COPY), (INFO), (OVERLAY) all have the same effect: (https://www.eecs.umich.edu/courses/eecs373/readings/Linker.pdf,
Diff Detail Event TimelineComment Actions For what it is worth COPY and OVERLAY are used quite a bit in embedded systems. The Arm GCC Embedded toolchain linker scripts in the sample directory use COPY to reserve an area for the heap and stack https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads .heap (COPY): { __end__ = .; PROVIDE(end = .); *(.heap*) __HeapLimit = .; } > RAM /* .stack_dummy section doesn't contains any symbols. It is only * used for linker to calculate size of stack sections, and assign * values to stack symbols later */ .stack_dummy (COPY): { *(.stack*) } > RAM I'd be very happy to see COPY implemented. Comment Actions I mean, for any language, if you google for some extremely minor feature of that language, I'm pretty sure that you can always find one. So the fact that you can find a use case on the internet isn't very convincing that we should support it. Comment Actions While these minor features are not used at all in a system sophisticated enough to run ELF files directly, I'd argue that at least COPY will be used heavily in embedded systems as placement of the heap and stack via symbols derived from linker script sections is a common idiom. Overlays are not so common these days but they still exist. It is true that we haven't got a large contingent of embedded developers using the Arm port, there are a few, but I'm hoping we don't scare them away. Comment Actions I inspected binutils bugtracker and found following issue: In short it was about that person was unable to use gold as a drop in replacement for bfd to link We were thinking about implementing features like "INSERT AFTER/INSERT BEFORE" which are probably even |
can be -> is