Fix meaning of generated .debug_loc
sections
#8753
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit is a fix to Wasmtime's DWARF processing transform to correct the meaning of the
.debug_loc
section. This section's addresses are relative to theDW_AT_low_pc
entry located in theDW_TAG_compile_unit
container, but Wasmtime's construction of this section didn't take this into account. Instead all addresses in.debug_loc
are relative to the start of the compiled object, not to the start of the compile unit itself. This commit fixes this by unconditionally describingDW_TAG_compile_unit
locations withDW_AT_ranges
instead ofDW_AT_low_pc
. This ends up fixing debug information for debug information using.debug_loc
with multiple codegen units.Closes #8752