projects / platform / upstream / llvm.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: c5e2085) | 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)
commit74f334e476a62d0ddcd4751d266560a503e00d55
tree3d7d2605cc28fb3aed01641a334b000311758a87tree | snapshot
parentc5e2085629069f44adbc6d193824484a91320843commit | 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>

llvm-svn: 169754
llvm/include/llvm/Transforms/Instrumentation.h diff | blob | history
llvm/lib/Transforms/Instrumentation/GCOVProfiling.cpp diff | blob | history
Domain: System / Toolchain;