The FILL command is similar to the ‘=fillexp’ output section attribute, but it only affects
the part of the section following the FILL command, rather than the entire section. If both
are used, the FILL command takes precedence.
This is PR30243
Paths
| Differential D24186
[ELF] - Linkerscript: implemented FILL command. AbandonedPublic Authored by grimar on Sep 2 2016, 6:00 AM.
Details
Diff Detail Event Timelinegrimar updated this object. Comment Actions Did you find any uses case of multiple FILL commands in one section definition? It seems to me that it's too complicated. I'd like to handle it as an alias to =<fillexp> feature. Comment Actions
I didn't yet. Not sure that simple alias will work here. FILL command only affects the part of the section following the FILL command. So it would be very different behavior in total even for simple case when single FILL is somewhere at the midde of section. I leaved a question on PR30243 page, let see if anyone knows the real life use cases for it. Comment Actions
I'm not aware of any uses for fine-grained control over fill values off hand, but I haven't looked in detail.
Revision Contents
Diff 70150 ELF/LinkerScript.h
ELF/LinkerScript.cpp
ELF/OutputSections.cpp
test/ELF/linkerscript/linkerscript-fill.s
test/ELF/linkerscript/linkerscript-sections-padding.s
|