aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Reader/MetadataLoader.cpp
diff options
context:
space:
mode:
authorMartin Storsjo <martin@martin.st>2018-01-24 06:40:11 +0000
committerMartin Storsjo <martin@martin.st>2018-01-24 06:40:11 +0000
commit4ed94a06ac0a4677501e4ac8e06e932dbb336876 (patch)
tree1c1486f3da25703844a6ed131f4b37b35451a7e2 /llvm/lib/Bitcode/Reader/MetadataLoader.cpp
parente8248f2e106e8a9ab3ddcce637a15e811300cc7a (diff)
downloadllvm-4ed94a06ac0a4677501e4ac8e06e932dbb336876.zip
llvm-4ed94a06ac0a4677501e4ac8e06e932dbb336876.tar.gz
llvm-4ed94a06ac0a4677501e4ac8e06e932dbb336876.tar.bz2
[ARM] Call __chkstk for dynamic stack allocation in all windows environments
This matches what MSVC does for alloca() function calls on ARM. Even if MSVC doesn't support VLAs at the language level, it does support the alloca function. On the clang level, both the _alloca() (when emulating MSVC, which is what the alloca() function expands to) and __builtin_alloca() builtin functions, and VLAs, map to the same LLVM IR "alloca" function - so within LLVM they're not distinguishable from each other. Differential Revision: https://reviews.llvm.org/D42292 llvm-svn: 323308
Diffstat (limited to 'llvm/lib/Bitcode/Reader/MetadataLoader.cpp')
0 files changed, 0 insertions, 0 deletions