projects / oota-llvm.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: f0d19bd) | patch
Don't use a red zone for code coverage if the user specified `-mno-red-zone'.
authorBill Wendling <isanbard@gmail.com>
Mon, 10 Dec 2012 19:46:49 +0000 (19:46 +0000)
committerBill Wendling <isanbard@gmail.com>
Mon, 10 Dec 2012 19:46:49 +0000 (19:46 +0000)
commit08e13e4488cde76fc51f942e773874627a88eeae
treeec5594c396378a6e99e7e38803609e8fa51bda7atree | snapshot
parentf0d19bd1291ee1d2ffee4bbe0aef12b814aff789commit | diff
Don't use a red zone for code coverage if the user specified `-mno-red-zone'.

The `-mno-red-zone' flag wasn't being propagated to the functions that code
coverage generates. This allowed some of them to use the red zone when that
wasn't allowed.
<rdar://problem/12843084>

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@169754 91177308-0d34-0410-b5e6-96231b3b80d8
include/llvm/Transforms/Instrumentation.h diff | blob | history
lib/Transforms/Instrumentation/GCOVProfiling.cpp diff | blob | history
C/C++ LLVM-based compilers that forbids OOTA behaviors