diff options
| author | David Blaikie <dblaikie@gmail.com> | 2021-08-14 12:46:08 -0700 |
|---|---|---|
| committer | David Blaikie <dblaikie@gmail.com> | 2021-08-15 11:40:24 -0700 |
| commit | 62a4c2c10e8eadd5bab49be72d642db257b46100 (patch) | |
| tree | 19ab270f7504d92f642cb7db8ecda890d3ddac0d /llvm/lib/Support/CommandLine.cpp | |
| parent | 786b8fcc9b1eed093926e6d9c36891ab72b7bde3 (diff) | |
| download | llvm-62a4c2c10e8eadd5bab49be72d642db257b46100.zip llvm-62a4c2c10e8eadd5bab49be72d642db257b46100.tar.gz llvm-62a4c2c10e8eadd5bab49be72d642db257b46100.tar.bz2 | |
DWARFVerifier: Check section-relative references at the end of the section
This ensures that debug_types references aren't looked for in
debug_info section.
Behavior is still going to be questionable in an unlinked object file -
since cross-cu references could refer to symbols in another .debug_info
(or, in theory, .debug_types) chunk - but if a producer only uses
ref_addr to refer to things within the same .debug_info chunk in an
object file (eg: whole program optimization/LTO - producing two CUs into
a single .debug_info section in an object file - the ref_addrs there
could be resolved relative to that .debug_info chunk, not needing to
consider comdat (DWARFv5 type units or other creatures) chunks of
.debug_info, etc)
Diffstat (limited to 'llvm/lib/Support/CommandLine.cpp')
0 files changed, 0 insertions, 0 deletions