Reid Kleckner 0f8f086e21 [ASan] Don't use stack malloc for 32-bit functions using inline asm ... This prevents us from running out of registers in the backend. Introducing stack malloc calls prevents the backend from recognizing the inline asm operands as stack objects. When the backend recognizes a stack object, it doesn't need to materialize the address of the memory in a physical register. Instead it generates a simple SP-based memory operand. Introducing a stack malloc forces the backend to find a free register for every memory operand. 32-bit x86 simply doesn't have enough registers for this to succeed in most cases. Reviewers: kcc, samsonov Differential Revision: http://reviews.llvm.org/D8790 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@233979 91177308-0d34-0410-b5e6-96231b3b80d8		2015-04-02 21:44:55 +00:00
..
AddressSanitizer	[ASan] Don't use stack malloc for 32-bit functions using inline asm	2015-04-02 21:44:55 +00:00
BoundsChecking	Add a bunch of CHECK missing colons in tests. NFC.	2015-03-14 01:43:57 +00:00
DataFlowSanitizer	DebugInfo: Move new hierarchy into place	2015-03-03 17:24:31 +00:00
InstrProfiling	[opaque pointer type] Add textual IR support for explicit type parameter to gep operator	2015-03-13 18:20:45 +00:00
MemorySanitizer	DebugInfo: Move new hierarchy into place	2015-03-03 17:24:31 +00:00
SanitizerCoverage	[sanitizer] experimental tracing for cmp instructions	2015-03-21 01:29:36 +00:00
ThreadSanitizer	[opaque pointer type] Add textual IR support for explicit type parameter to gep operator	2015-03-13 18:20:45 +00:00