aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
diff options
context:
space:
mode:
authorAlexander Yermolovich <ayermolo@fb.com>2022-01-31 11:06:06 -0800
committerAlexander Yermolovich <ayermolo@fb.com>2022-01-31 11:10:23 -0800
commit9f3f9d19c7edc99a1450ee15d7cde67a67eb445d (patch)
tree57c714c884ff0f3ada6aad9e8c621c3890515e2f /llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
parent804915f5dca4db5a33c305d85331f3950147753f (diff)
downloadllvm-9f3f9d19c7edc99a1450ee15d7cde67a67eb445d.zip
llvm-9f3f9d19c7edc99a1450ee15d7cde67a67eb445d.tar.gz
llvm-9f3f9d19c7edc99a1450ee15d7cde67a67eb445d.tar.bz2
[BOLT][DWARF] Handle shared abbrev section
We can have a scenario where multiple CUs share an abbrev table. We modify or don't modify one CU, which leads to other CUs having invalid abbrev section. Example that caused it. All of CUs shared the same abbrev table. First CU just had compile_unit and sub_program. It was not modified. Next CU had DW_TAG_lexical_block with DW_AT_low_pc/DW_AT_high_pc converted to DW_AT_low_pc/DW_AT_ranges. We used unmodified abbrev section for first and subsequent CUs. So when parsing subsequent CUs debug info was corrupted. In this patch we will now duplicate all sections that are modified and are different. This also means that if .debug_types is present and it shares Abbrev table, and they usually are, we now can have two Abbrev tables. One for CU that was modified, and unmodified one for TU. Reviewed By: maksfb Differential Revision: https://reviews.llvm.org/D118517
Diffstat (limited to 'llvm/lib/Bitcode/Writer/BitcodeWriter.cpp')
0 files changed, 0 insertions, 0 deletions