summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Analysis/LazyValueInfo.cpp
diff options
context:
space:
mode:
authorBob Wilson <bob.wilson@apple.com>2010-08-27 23:18:17 +0000
committerBob Wilson <bob.wilson@apple.com>2010-08-27 23:18:17 +0000
commit13ce07fa928ba20d6369195dd62bc3599172bf16 (patch)
tree5a1f9f8918b2465c92492e6af373747d228c9cdd /llvm/lib/Analysis/LazyValueInfo.cpp
parent954e9557e3b2bbc712a4a2f81cb443a831ea3c45 (diff)
downloadbcm5719-llvm-13ce07fa928ba20d6369195dd62bc3599172bf16.tar.gz
bcm5719-llvm-13ce07fa928ba20d6369195dd62bc3599172bf16.zip
Change ARM VFP VLDM/VSTM instructions to use addressing mode #4, just like
all the other LDM/STM instructions. This fixes asm printer crashes when compiling with -O0. I've changed one of the NEON tests (vst3.ll) to run with -O0 to check this in the future. Prior to this change VLDM/VSTM used addressing mode #5, but not really. The offset field was used to hold a count of the number of registers being loaded or stored, and the AM5 opcode field was expanded to specify the IA or DB mode, instead of the standard ADD/SUB specifier. Much of the backend was not aware of these special cases. The crashes occured when rewriting a frameindex caused the AM5 offset field to be changed so that it did not have a valid submode. I don't know exactly what changed to expose this now. Maybe we've never done much with -O0 and NEON. Regardless, there's no longer any reason to keep a count of the VLDM/VSTM registers, so we can use addressing mode #4 and clean things up in a lot of places. llvm-svn: 112322
Diffstat (limited to 'llvm/lib/Analysis/LazyValueInfo.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud