Skip to content

Commit 091da2d

Browse files
committed
[CodeGen][PowerPC] Add codegen test for TLS stack canary
Make sure the code generated for a TLS-relative stack guard canary references the right location before and after intervening function code. Signed-off-by: Keith Packard <[email protected]>
1 parent d0beb6a commit 091da2d

File tree

1 file changed

+114
-0
lines changed

1 file changed

+114
-0
lines changed
Lines changed: 114 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,114 @@
1+
; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py UTC_ARGS: --version 5
2+
; RUN: llc -mtriple=powerpc64 -verify-machineinstrs < %s \
3+
; RUN: | FileCheck %s --check-prefixes=BE64
4+
; RUN: llc -mtriple=powerpc64le -verify-machineinstrs < %s \
5+
; RUN: | FileCheck %s --check-prefixes=LE64
6+
; RUN: llc -mtriple=ppc32 -verify-machineinstrs < %s \
7+
; RUN: | FileCheck %s --check-prefixes=LE32
8+
9+
define void @foo(i64 %t) sspstrong nounwind {
10+
; BE64-LABEL: foo:
11+
; BE64: # %bb.0:
12+
; BE64-NEXT: mflr 0
13+
; BE64-NEXT: std 31, -8(1)
14+
; BE64-NEXT: stdu 1, -144(1)
15+
; BE64-NEXT: std 0, 160(1)
16+
; BE64-NEXT: sldi 3, 3, 2
17+
; BE64-NEXT: mr 31, 1
18+
; BE64-NEXT: ld 4, 500(13)
19+
; BE64-NEXT: addi 3, 3, 15
20+
; BE64-NEXT: rldicr 3, 3, 0, 59
21+
; BE64-NEXT: neg 3, 3
22+
; BE64-NEXT: std 4, 128(31)
23+
; BE64-NEXT: addi 4, 31, 144
24+
; BE64-NEXT: stdux 4, 1, 3
25+
; BE64-NEXT: addi 3, 1, 112
26+
; BE64-NEXT: bl baz
27+
; BE64-NEXT: nop
28+
; BE64-NEXT: ld 3, 500(13)
29+
; BE64-NEXT: ld 4, 128(31)
30+
; BE64-NEXT: cmpld 3, 4
31+
; BE64-NEXT: bne- 0, .LBB0_2
32+
; BE64-NEXT: # %bb.1: # %SP_return
33+
; BE64-NEXT: ld 1, 0(1)
34+
; BE64-NEXT: ld 0, 16(1)
35+
; BE64-NEXT: ld 31, -8(1)
36+
; BE64-NEXT: mtlr 0
37+
; BE64-NEXT: blr
38+
; BE64-NEXT: .LBB0_2: # %CallStackCheckFailBlk
39+
; BE64-NEXT: bl __stack_chk_fail
40+
; BE64-NEXT: nop
41+
;
42+
; LE64-LABEL: foo:
43+
; LE64: # %bb.0:
44+
; LE64-NEXT: mflr 0
45+
; LE64-NEXT: std 31, -8(1)
46+
; LE64-NEXT: stdu 1, -64(1)
47+
; LE64-NEXT: sldi 3, 3, 2
48+
; LE64-NEXT: std 0, 80(1)
49+
; LE64-NEXT: mr 31, 1
50+
; LE64-NEXT: addi 3, 3, 15
51+
; LE64-NEXT: ld 4, 500(13)
52+
; LE64-NEXT: rldicr 3, 3, 0, 59
53+
; LE64-NEXT: std 4, 48(31)
54+
; LE64-NEXT: addi 4, 31, 64
55+
; LE64-NEXT: neg 3, 3
56+
; LE64-NEXT: stdux 4, 1, 3
57+
; LE64-NEXT: addi 3, 1, 32
58+
; LE64-NEXT: bl baz
59+
; LE64-NEXT: nop
60+
; LE64-NEXT: ld 3, 500(13)
61+
; LE64-NEXT: ld 4, 48(31)
62+
; LE64-NEXT: cmpld 3, 4
63+
; LE64-NEXT: bne- 0, .LBB0_2
64+
; LE64-NEXT: # %bb.1: # %SP_return
65+
; LE64-NEXT: ld 1, 0(1)
66+
; LE64-NEXT: ld 0, 16(1)
67+
; LE64-NEXT: ld 31, -8(1)
68+
; LE64-NEXT: mtlr 0
69+
; LE64-NEXT: blr
70+
; LE64-NEXT: .LBB0_2: # %CallStackCheckFailBlk
71+
; LE64-NEXT: bl __stack_chk_fail
72+
; LE64-NEXT: nop
73+
;
74+
; LE32-LABEL: foo:
75+
; LE32: # %bb.0:
76+
; LE32-NEXT: mflr 0
77+
; LE32-NEXT: stwu 1, -32(1)
78+
; LE32-NEXT: stw 31, 28(1)
79+
; LE32-NEXT: slwi 4, 4, 2
80+
; LE32-NEXT: stw 0, 36(1)
81+
; LE32-NEXT: addi 4, 4, 15
82+
; LE32-NEXT: lwz 3, 500(2)
83+
; LE32-NEXT: mr 31, 1
84+
; LE32-NEXT: rlwinm 4, 4, 0, 0, 27
85+
; LE32-NEXT: neg 4, 4
86+
; LE32-NEXT: stw 3, 24(31)
87+
; LE32-NEXT: addi 3, 31, 32
88+
; LE32-NEXT: stwux 3, 1, 4
89+
; LE32-NEXT: addi 3, 1, 16
90+
; LE32-NEXT: bl baz
91+
; LE32-NEXT: lwz 3, 500(2)
92+
; LE32-NEXT: lwz 4, 24(31)
93+
; LE32-NEXT: cmplw 3, 4
94+
; LE32-NEXT: bne- 0, .LBB0_2
95+
; LE32-NEXT: # %bb.1: # %SP_return
96+
; LE32-NEXT: lwz 31, 0(1)
97+
; LE32-NEXT: lwz 0, -4(31)
98+
; LE32-NEXT: mr 1, 31
99+
; LE32-NEXT: mr 31, 0
100+
; LE32-NEXT: lwz 0, 4(1)
101+
; LE32-NEXT: mtlr 0
102+
; LE32-NEXT: blr
103+
; LE32-NEXT: .LBB0_2: # %CallStackCheckFailBlk
104+
; LE32-NEXT: bl __stack_chk_fail
105+
%vla = alloca i32, i64 %t, align 4
106+
call void @baz(ptr %vla)
107+
ret void
108+
}
109+
110+
declare void @baz(ptr)
111+
112+
!llvm.module.flags = !{!1, !2}
113+
!1 = !{i32 2, !"stack-protector-guard", !"tls"}
114+
!2 = !{i32 2, !"stack-protector-guard-offset", i32 500}

0 commit comments

Comments
 (0)