summaryrefslogtreecommitdiffstats
path: root/llvm/test/Bitcode/atomic.ll
diff options
context:
space:
mode:
authorAhmed Bougacha <ahmed.bougacha@gmail.com>2015-04-01 00:45:09 +0000
committerAhmed Bougacha <ahmed.bougacha@gmail.com>2015-04-01 00:45:09 +0000
commit408d010a7cfc97065d71869de2209b6f3681d0ce (patch)
tree8d83f913fe2ae53598264b831561bc201a6eced7 /llvm/test/Bitcode/atomic.ll
parent50271aae7e0f7c560121f70245537e4b3d66dc42 (diff)
downloadbcm5719-llvm-408d010a7cfc97065d71869de2209b6f3681d0ce.tar.gz
bcm5719-llvm-408d010a7cfc97065d71869de2209b6f3681d0ce.zip
[SimplifyLibCalls] Ignore nobuiltin/unavailable fortified libcalls.
We used to do this before refactorings around r225640. Some clang users checked for _chk libcall availability using: __has_builtin(__builtin___memcpy_chk) When compiling with -fno-builtin, this is always true. When passing -ffreestanding/-mkernel, which both imply -fno-builtin, we end up with fortified libcalls, which isn't acceptable in a freestanding environment which only provides their non-fortified counterparts. Until we change clang and/or teach external users to check for availability differently, disregard the "nobuiltin" attribute and TLI::has. Workaround for PR23093. llvm-svn: 233776
Diffstat (limited to 'llvm/test/Bitcode/atomic.ll')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud