summaryrefslogtreecommitdiffstats
path: root/lld/test/ELF/linkerscript/ttext-script.s
Commit message (Collapse)AuthorAgeFilesLines
* [llvm-readobj] llvm-readobj --elf-output-style=GNU => llvm-readelfFangrui Song2019-05-011-1/+1
| | | | | | | While updating the test, change -l -S to -S -l as the output of -S goes before -l. llvm-svn: 359653
* [test] Change llvm-readobj -long-option to --long-option or well-known short ↵Fangrui Song2019-05-011-1/+1
| | | | | | | | | | | | options. NFC Also change some options that have different semantics (cause confusion) in llvm-readelf mode: -s => -S -t => --symbols -sd => --section-data llvm-svn: 359651
* Prefer -Ttext over linker script values.Rafael Espindola2017-06-201-0/+11
I found this while trying to build u-boot. It uses -Ttext in combination with linker scripts. My first reaction was to change the linker scripts to have the correct value, but I found that it is actually quite convenient to have -Ttext take precedence. By having just .text : { *(.text) } In the script, they can define the text address in a single Makefile and pass it to ld with -Ttext and for the C code with -DFoo=value. Doing the same with linker scripts would require them to be generated during the build. llvm-svn: 305766
OpenPOWER on IntegriCloud