Simplify dbg.value handling in SDISel with early returns
authorReid Kleckner <rnk@google.com>
Fri, 5 May 2017 18:30:34 +0000 (18:30 +0000)
committerReid Kleckner <rnk@google.com>
Fri, 5 May 2017 18:30:34 +0000 (18:30 +0000)
commitac1a97b32fbc2d8f1a95f76714c5b729b6f251ce
tree0398dafae567af82796b8fb04b133d1dce65cbd2
parent03cdd1241fc256bc3daf22da33e76f3afd249c5b
Simplify dbg.value handling in SDISel with early returns

No functional change other than improving dbgs logging accuracy on
constant dbg values. Previously we would add things like "i32 42" as
debug values, and then log that we were dropping the debug info, which
is silly.

Delete some dead code that was checking for static allocas. This
remained after r207165, but served no purpose. Currently, static alloca
dbg.values are always sent through the DanglingDebugInfoMap, and are
usually made valid the first time the alloca is used.

llvm-svn: 302267
llvm/lib/CodeGen/SelectionDAG/SelectionDAGBuilder.cpp