diff options
| author | Jeremy Morse <jeremy.morse.llvm@gmail.com> | 2019-01-29 09:40:05 +0000 |
|---|---|---|
| committer | Jeremy Morse <jeremy.morse.llvm@gmail.com> | 2019-01-29 09:40:05 +0000 |
| commit | 66ac86b58d2f5b8a15c42ea2cd32f4cdd19fd6ff (patch) | |
| tree | db0ce4a044ecc3d0cc2a6c3f05ef3a4f694f4268 /llvm/lib/Target/WebAssembly/WebAssemblyFixFunctionBitcasts.cpp | |
| parent | 23e642248d0713ccf0b257c79083ca856f74b77c (diff) | |
| download | llvm-66ac86b58d2f5b8a15c42ea2cd32f4cdd19fd6ff.zip llvm-66ac86b58d2f5b8a15c42ea2cd32f4cdd19fd6ff.tar.gz llvm-66ac86b58d2f5b8a15c42ea2cd32f4cdd19fd6ff.tar.bz2 | |
[DebugInfo][DAG] Process FrameIndex dbg.values unconditionally
A FrameIndex should be valid throughout a block regardless of what instructions
get selected in that block -- therefore we shouldn't harness dbg.values that
refer to FrameIndexes to an SDNode. There are numerous codegen reasons why
an SDNode never appears or doesn't become a location that a DBG_VALUE can
refer to. None of them actually affect the variable location.
Therefore, before any other tests to encode dbg_values in a SelectionDAG,
identify FrameIndex operands and encode them unattached to any SDNode.
Differential Revision: https://reviews.llvm.org/D57328
llvm-svn: 352467
Diffstat (limited to 'llvm/lib/Target/WebAssembly/WebAssemblyFixFunctionBitcasts.cpp')
0 files changed, 0 insertions, 0 deletions