summaryrefslogtreecommitdiffstats
path: root/lld/test/ELF/linkerscript/data-commands.s
Commit message (Collapse)AuthorAgeFilesLines
* Convert more tests as linker scripts instead of assembly.Rui Ueyama2018-03-011-117/+0
| | | | llvm-svn: 326415
* Fix output section offset and contents when linker script uses memory region ↵Rafael Espindola2017-12-241-0/+36
| | | | | | | | | | | | | | | | | and data commands. Advance the memory region offset when handling a linker script data command such as BYTE or LONG. Failure to advance the offset results in corrupted output with overlapping sections. Update tests to check for this combination of both a) memory regions and b) data commands. Fixes https://bugs.llvm.org/show_bug.cgi?id=35565 Patch by Owen Shaw! llvm-svn: 321418
* [ELF] Fix test case thinko from r289152Meador Inge2016-12-091-5/+1
| | | | | | | It was pointed out in a post-commit review that the tests were structured oddly. Fixed thusly. llvm-svn: 289278
* [ELF] Allow output section data commands to take expressionsMeador Inge2016-12-081-1/+46
| | | | | | | | | | | | The current implementation of the output section data store commands can only handle integer literals, but it should really handle arbitrary expressions [1]. This commit fixes that. [1] https://sourceware.org/binutils/docs-2.27/ld/Output-Section-Data.html#Output-Section-Data Differential Revision: https://reviews.llvm.org/D27561 llvm-svn: 289152
* [ELF] - Linkerscript: implemented BYTE/SHORT/LONG/QUAD commands.George Rimar2016-09-261-0/+40
The BYTE, SHORT, LONG, and QUAD commands store one, two, four, and eight bytes (respectively). After storing the bytes, the location counter is incremented by the number of bytes stored. Previously our scripts handles these commands incorrectly. For example: SECTIONS { .foo : { *(.foo.1) BYTE(0x11) ... We accepted the script above treating BYTE as input section description. These commands are used in the wild though. Differential revision: https://reviews.llvm.org/D24830 llvm-svn: 282429
OpenPOWER on IntegriCloud