mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-10-20 19:42:54 +02:00
3a75cd4bf9
With this change, ideally IR pass can always generate llvm.stackguard call to get the stack guard; but for now there are still IR form stack guard customizations around (see getIRStackGuard()). Future SSP customization should go through LOAD_STACK_GUARD. There is a behavior change: stack guard values are not CSEed anymore, since we should never reuse the value in case that it has been spilled (and corrupted). See ssp-guard-spill.ll. This also cause the change of stack size and codegen in X86 and AArch64 test cases. Ideally we'd like to know if the guard created in llvm.stackprotector() gets spilled or not. If the value is spilled, discard the value and reload stack guard; otherwise reuse the value. This can be done by teaching register allocator to know how to rematerialize LOAD_STACK_GUARD and force a rematerialization (which seems hard), or check for spilling in expandPostRAPseudo. It only makes sense when the stack guard is a global variable, which requires more instructions to load. Anyway, this seems to go out of the scope of the current patch. llvm-svn: 266806
25 lines
755 B
LLVM
25 lines
755 B
LLVM
; RUN: llc -mtriple x86_64-apple-macosx10.8.0 -warn-stack-size=80 < %s 2>&1 >/dev/null | FileCheck %s
|
|
; Check the internal option that warns when the stack size exceeds the
|
|
; given amount.
|
|
; <rdar://13987214>
|
|
|
|
; CHECK-NOT: nowarn
|
|
define void @nowarn() nounwind ssp {
|
|
entry:
|
|
%buffer = alloca [12 x i8], align 1
|
|
%arraydecay = getelementptr inbounds [12 x i8], [12 x i8]* %buffer, i64 0, i64 0
|
|
call void @doit(i8* %arraydecay) nounwind
|
|
ret void
|
|
}
|
|
|
|
; CHECK: warning: stack size limit exceeded (88) in warn
|
|
define void @warn() nounwind ssp {
|
|
entry:
|
|
%buffer = alloca [80 x i8], align 1
|
|
%arraydecay = getelementptr inbounds [80 x i8], [80 x i8]* %buffer, i64 0, i64 0
|
|
call void @doit(i8* %arraydecay) nounwind
|
|
ret void
|
|
}
|
|
|
|
declare void @doit(i8*)
|