summaryrefslogtreecommitdiffstats
path: root/clang/lib/StaticAnalyzer/Core/SimpleConstraintManager.cpp
diff options
context:
space:
mode:
authorTim Northover <tnorthover@apple.com>2014-05-26 17:22:07 +0000
committerTim Northover <tnorthover@apple.com>2014-05-26 17:22:07 +0000
commit68ae503de92f3227ce34926ed4467cea3481f61d (patch)
tree87f55bd74e207eeaff9d31235b2963c3f53f18ab /clang/lib/StaticAnalyzer/Core/SimpleConstraintManager.cpp
parent47e003c65d11fcf1d8eddc0b7dcea6a615f6b20e (diff)
downloadbcm5719-llvm-68ae503de92f3227ce34926ed4467cea3481f61d.tar.gz
bcm5719-llvm-68ae503de92f3227ce34926ed4467cea3481f61d.zip
AArch64: force i1 to be zero-extended at an ABI boundary.
This commit is debatable. There are two possible approaches, neither of which is really satisfactory: 1. Use "@foo(i1 zeroext)" to mean an extension to 32-bits on Darwin, and 8 bits otherwise. 2. Redefine "@foo(i1)" to mean that the i1 is extended by the caller to 8 bits. This goes against the spirit of "zeroext" I think, but it's a bit of a vague construct anyway (by definition you're going to extend to the amount required by the ABI, that's why it's the ABI!). This implements option 2. The DAG machinery really isn't setup for the first (there's a fairly strong assumption that "zeroext" goes to at least the smallest register size), and even if it was the resulting DAG looks like it would be inferior in many cases. Theoretically we could add AssertZext nodes in the consumers of ABI-passed values too now, but this actually seems to make the code worse in practice by making truncation proceed in two steps. The code produced is equally valid if we continue to assume only the low bit is defined. Should fix PR19850 llvm-svn: 209637
Diffstat (limited to 'clang/lib/StaticAnalyzer/Core/SimpleConstraintManager.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud