summaryrefslogtreecommitdiffstats
path: root/lld/test/ELF/gdb-index-ranges.s
Commit message (Collapse)AuthorAgeFilesLines
* [ELF][X86] Allow PT_LOAD to have overlapping p_offset ranges on EM_X86_64Fangrui Song2019-09-161-2/+2
| | | | | | | | Port the D64906 technique to EM_X86_64. Differential Revision: https://reviews.llvm.org/D67482 llvm-svn: 371958
* [DWARF] Fix typo, .gnu_index -> .gdb_indexFangrui Song2018-11-021-1/+1
| | | | llvm-svn: 346040
* Update testcases for llvm-dwarfdump command line interface changeAdrian Prantl2017-09-111-1/+1
| | | | llvm-svn: 312974
* [ELF] - Added testcase gdb-index-ranges.s (https://reviews.llvm.org/D32750)George Rimar2017-05-031-0/+66
Before rL301170 was landed, LLD did not produce correct entries in .gdb_index address area. Issue was fixed on LLVM DWARF parsers side and was relative to how .debug_ranges section was scanned. It was main problem of PR32319. It makes sense to have testcase on LLD size too. This checks that we generate proper values now, because we do not have any tests for .gdb_index which works with .debug_ranges atm. Differential revision: https://reviews.llvm.org/D32750 llvm-svn: 302006
OpenPOWER on IntegriCloud