summaryrefslogtreecommitdiffstats
path: root/llvm/tools/llvm-readobj/llvm-readobj.cpp
diff options
context:
space:
mode:
authorReid Kleckner <rnk@google.com>2017-09-20 18:19:08 +0000
committerReid Kleckner <rnk@google.com>2017-09-20 18:19:08 +0000
commit4e040287919c339506d6f795e42b41325fd22171 (patch)
tree464f82f4c71958684d5e213681fc7e12820643a3 /llvm/tools/llvm-readobj/llvm-readobj.cpp
parent6c84ffbf5fd9d50995eee0a8fbf9efafe08790d7 (diff)
downloadbcm5719-llvm-4e040287919c339506d6f795e42b41325fd22171.tar.gz
bcm5719-llvm-4e040287919c339506d6f795e42b41325fd22171.zip
Re-land "[DebugInfo] Insert DW_OP_deref when spilling indirect DBG_VALUEs"
After r313775, it's easier to maintain a parallel BitVector of spilled locations indexed by location number. I wasn't able to build a good reduced test case for this iteration of the bug, but I added a more direct assertion that spilled values must use frame index locations. If this bug reappears, it won't only fire on the NEON vector code that we detected it on, but on medium-sized integer-only programs as well. llvm-svn: 313786
Diffstat (limited to 'llvm/tools/llvm-readobj/llvm-readobj.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud