aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Object/WasmObjectFile.cpp
diff options
context:
space:
mode:
authorWei Wang <apollo.mobility@gmail.com>2024-01-02 09:54:16 -0800
committerGitHub <noreply@github.com>2024-01-02 09:54:16 -0800
commit9c978c94187511326627c34fb04c57f853c488fc (patch)
treec24f1dae3d15a92fa9b77dcc66f33accbf6a8655 /llvm/lib/Object/WasmObjectFile.cpp
parentbf684a97f37b12ccf2c98b007b8222c54c7480f5 (diff)
downloadllvm-9c978c94187511326627c34fb04c57f853c488fc.zip
llvm-9c978c94187511326627c34fb04c57f853c488fc.tar.gz
llvm-9c978c94187511326627c34fb04c57f853c488fc.tar.bz2
[coroutines] Use DILocation from new storage for hoisted dbg.declare (#75402)
Make the hoisted dbg.declare inherent the DILocation scope from the new storage. After hoisting, the dbg.declare is moved into the block that defines the new storage. This could create an inconsistency in the debug location scope hierarchy where the scope of hoisted dbg.declare (i.e. DILexicalBlock) is enclosed with the scope of the block (i.e. DISubprogram). This confuses LiveDebugValues pass to think that the hoisted dbg.declare is killed in that block and does not generate DBG_VALUE in other blocks. Debugger won't be able to track its value anymore. We do this for unoptimized binary only.
Diffstat (limited to 'llvm/lib/Object/WasmObjectFile.cpp')
0 files changed, 0 insertions, 0 deletions