aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/Basic/SourceManager.cpp
diff options
context:
space:
mode:
authorFangrui Song <i@maskray.me>2020-10-19 16:45:56 -0700
committerFangrui Song <i@maskray.me>2020-10-20 09:35:32 -0700
commit38b632c16e0fdfd5f5a69bcfd4aecf6f69ea0186 (patch)
tree2f07259ea67d12d369529478102c1299cf41f6e1 /clang/lib/Basic/SourceManager.cpp
parentcc07fbe37dc82eeb3e6261a4c54f44b22cbb531d (diff)
downloadllvm-38b632c16e0fdfd5f5a69bcfd4aecf6f69ea0186.zip
llvm-38b632c16e0fdfd5f5a69bcfd4aecf6f69ea0186.tar.gz
llvm-38b632c16e0fdfd5f5a69bcfd4aecf6f69ea0186.tar.bz2
[ELF] --gdb-index: support --icf={safe,all}
The combination has not been tested before. In the case of ICF, `e.section->getVA(0)` equals the start address of the output section. This can cause incorrect overlapping with the actual function at the start of the output section and potentially trigger a GDB internal error in `dw2_find_pc_sect_compunit_symtab` (presumably because: if a short address range incorrectly starts at the start address of the output section, GDB may pick it instead of the correct longer address range. When mapping an address within the long address range but out of the scope of the short address range, the routine may find nothing - while the code asserts that it can find something). Note that in the case of ICF there may be duplicate address range entries, but GDB appears to be fine with them. Reviewed By: grimar Differential Revision: https://reviews.llvm.org/D89751
Diffstat (limited to 'clang/lib/Basic/SourceManager.cpp')
0 files changed, 0 insertions, 0 deletions