summaryrefslogtreecommitdiffstats
path: root/lld/test/ELF/gc-debuginfo-tls.s
Commit message (Collapse)AuthorAgeFilesLines
* [test] Change llvm-readobj -long-option to --long-option or well-known short ↵Fangrui Song2019-05-011-2/+2
| | | | | | | | | | | | 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
* [lld] Add REQUIRES: x86 where needed to testsJoel Jones2018-06-061-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | If building lld without x86 support, tests that require that support should be treated as unsupported, not errors. Tested using: 1. cmake '-DLLVM_TARGETS_TO_BUILD=AArch64;X86' make check-lld => Expected Passes : 1406 Unsupported Tests : 287 2. cmake '-DLLVM_TARGETS_TO_BUILD=AArch64' make check-lld => Expected Passes : 410 Unsupported Tests : 1283 Patch by Joel Jones Differential Revision: https://reviews.llvm.org/D47748 llvm-svn: 334095
* Fix wrong TLS symbol values.Rui Ueyama2017-02-281-1/+1
| | | | | | | | | | I do not fully understand why we had these values in the tests, but the new value matches what ld.bfd and ld.gold set, so I guess that was just a mistake. Differential Revision: https://reviews.llvm.org/D30441 llvm-svn: 296505
* [ELF] - Fix confusing gc-debuginfo-tls.s testcase. NFC.George Rimar2017-02-281-9/+9
| | | | | | | It checked name from one symbol and other data from another before. llvm-svn: 296457
* Update for llvm change.Rafael Espindola2017-02-021-1/+1
| | | | llvm-svn: 293937
* [ELF/GC] Fix pending references to garbage collected sections.Davide Italiano2016-11-011-0/+23
The example reported in PR30793 shows a case where gc reclaims a SHF_TLS section, but it doesn't reclaim the section containing the debug info for it. This is expected, as we do not reclaim non-alloc sections during the garbage collection phase (and this is not going to change anytime soon, at least this is what I gathered last I talked with Rafael about it). So, we end up with a pending reference, thinking that the input was invalid (which is not true, as it's GC that removed the SHT_TLS section, and therefore didn't create the PT_TLS *segment* for it). In cases like this, just assign a VA of zero at relocation time instead of error'ing out (this is what gold does as well, FWIW). Differential Revision: https://reviews.llvm.org/D26201 llvm-svn: 285735
OpenPOWER on IntegriCloud