mirror of
https://github.com/RPCS3/llvm.git
synced 2025-05-16 18:35:53 +00:00
ed5107d663
On SparcV8, it was previously the case that a variable-sized alloca might overlap by 4-bytes the last fixed stack variable, effectively because 92 (the number of bytes reserved for the register spill area) != 96 (the offset added to SP for where to start a DYNAMIC_STACKALLOC). It's not as simple as changing 96 to 92, because variables that should be 8-byte aligned would then be misaligned. For now, simply increase the allocation size by 8 bytes for each dynamic allocation -- wastes space, but at least doesn't overlap. As the large comment says, doing this more efficiently will require larger changes in llvm. Also adds some test cases showing that we continue to not support dynamic stack allocation and over-alignment in the same function. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@285131 91177308-0d34-0410-b5e6-96231b3b80d8
21 lines
750 B
LLVM
21 lines
750 B
LLVM
; RUN: llc -march=sparc < %s | FileCheck %s
|
|
declare void @stack_realign_helper(i32 %a, i32* %b)
|
|
|
|
;; This is a function where we have a local variable of 64-byte
|
|
;; alignment. We want to see that the stack is aligned (the initial
|
|
;; andn), that the local var is accessed via stack pointer (to %o1), and that
|
|
;; the argument is accessed via frame pointer not stack pointer (to %o0).
|
|
|
|
;; CHECK-LABEL: stack_realign:
|
|
;; CHECK: andn %sp, 63, %sp
|
|
;; CHECK-NEXT: ld [%fp+92], %o0
|
|
;; CHECK-NEXT: call stack_realign_helper
|
|
;; CHECK-NEXT: add %sp, 128, %o1
|
|
|
|
define void @stack_realign(i32 %a, i32 %b, i32 %c, i32 %d, i32 %e, i32 %f, i32 %g) {
|
|
entry:
|
|
%aligned = alloca i32, align 64
|
|
call void @stack_realign_helper(i32 %g, i32* %aligned)
|
|
ret void
|
|
}
|