summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Target/ARM/ARMConstantPoolValue.cpp
diff options
context:
space:
mode:
authorJordan Rose <jordan_rose@apple.com>2012-12-21 18:26:48 +0000
committerJordan Rose <jordan_rose@apple.com>2012-12-21 18:26:48 +0000
commit7b5bfc795a29af1ba60706555091b31836d84c05 (patch)
tree86fe72e3931736f198a89b0032496141460e8f30 /llvm/lib/Target/ARM/ARMConstantPoolValue.cpp
parent8f83ee46ba9f817307f2561f7ad8c5c8bf254107 (diff)
downloadbcm5719-llvm-7b5bfc795a29af1ba60706555091b31836d84c05.tar.gz
bcm5719-llvm-7b5bfc795a29af1ba60706555091b31836d84c05.zip
[analyzer] Don't perform an expensive assertion in release builds.
Unfortunately, we don't seem to have a standard way to do this. I'm using the __OPTIMIZE__ GNU extension that Clang also defines, but that doesn't help MSVC. I suppose we could remove the check entirely, but it's useful for developing new constraint managers. llvm-svn: 170915
Diffstat (limited to 'llvm/lib/Target/ARM/ARMConstantPoolValue.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud