1 ; RUN: llc -mtriple=aarch64-none-linux-gnu < %s -o - | FileCheck %s
3 ; The following functions test the use case where an X constraint is used to
4 ; add a dependency between an assembly instruction (vmsr in this case) and
5 ; another instruction. In each function, we use a different type for the
6 ; X constraint argument.
8 ; We can something similar from the following C code:
9 ; double f1(double f, int pscr_value) {
10 ; asm volatile("msr fpsr,%1" : "=X" ((f)): "r" (pscr_value));
18 define double @f1(double %f, i32 %pscr_value) {
20 %f.addr = alloca double, align 8
21 store double %f, double* %f.addr, align 8
22 call void asm sideeffect "msr fpsr,$1", "=*X,r"(double* nonnull %f.addr, i32 %pscr_value) nounwind
23 %0 = load double, double* %f.addr, align 8
24 %add = fadd double %0, %0
28 ; int f2(int f, int pscr_value) {
29 ; asm volatile("msr fpsr,$1" : "=X" ((f)): "r" (pscr_value));
36 define i32 @f2(i32 %f, i32 %pscr_value) {
38 %f.addr = alloca i32, align 4
39 store i32 %f, i32* %f.addr, align 4
40 call void asm sideeffect "msr fpsr,$1", "=*X,r"(i32* nonnull %f.addr, i32 %pscr_value) nounwind
41 %0 = load i32, i32* %f.addr, align 4
46 ; typedef signed char int8_t;
47 ; typedef __attribute__((neon_vector_type(8))) int8_t int8x8_t;
50 ; int8x8_t vector_res_int8x8;
52 ; asm volatile ("msr fpsr,$1" : "=X" ((vector_res_int8x8)) : "r" (fpscr));
53 ; return vector_res_int8x8 * vector_res_int8x8;
59 define <8 x i8> @f3() {
61 %vector_res_int8x8 = alloca <8 x i8>, align 8
62 %0 = getelementptr inbounds <8 x i8>, <8 x i8>* %vector_res_int8x8, i32 0, i32 0
63 call void asm sideeffect "msr fpsr,$1", "=*X,r"(<8 x i8>* nonnull %vector_res_int8x8, i32 undef) nounwind
64 %1 = load <8 x i8>, <8 x i8>* %vector_res_int8x8, align 8
65 %mul = mul <8 x i8> %1, %1
69 ; We can emit integer constants.
70 ; We can get this from:
73 ; asm volatile ("add x0, x0, %0" : : "X" (x));
77 ; CHECK: add x0, x0, #2
80 tail call void asm sideeffect "add x0, x0, $0", "X"(i32 2)
84 ; We can emit function labels. This is equivalent to the following C code:
86 ; void (*x)(void) = &foo;
87 ; asm volatile ("bl %0" : : "X" (x));
93 tail call void asm sideeffect "bl $0", "X"(void ()* nonnull @f4)
97 declare void @foo(...)
99 ; This tests the behavior of the X constraint when used on functions pointers,
100 ; or functions with a cast. In the first asm call we figure out that this
101 ; is a function pointer and emit the label. However, in the second asm call
102 ; we can't see through the bitcast and we end up having to lower this constraint
103 ; to something else. This is not ideal, but it is a correct behaviour according
104 ; to the definition of the X constraint.
106 ; In this case (and other cases where we could have emitted something else),
107 ; what we're doing with the X constraint is not particularly useful either,
108 ; since the user could have used "r" in this situation for the same effect.
114 define void @f6() nounwind {
116 tail call void asm sideeffect "bl $0", "X"(void (...)* @foo) nounwind
117 tail call void asm sideeffect "br $0", "X"(void (...)* bitcast (void ()* @f4 to void (...)*)) nounwind
121 ; The following IR can be generated from C code with a function like:
124 ; asm volatile ("bl %0" : : "X" (a));
129 ; Ideally this would give the block address of bb, but it requires us to see
130 ; through blockaddress, which we can't do at the moment. This might break some
131 ; existing use cases where a user would expect to get a block label and instead
132 ; gets the block address in a register. However, note that according to the
133 ; "no constraints" definition this behaviour is correct (although not very nice).
138 call void asm sideeffect "br $0", "X"( i8* blockaddress(@f7, %bb) )
144 ; If we use a constraint "=*X", we should get a store back to *%x (in x0).
146 ; CHECK: add [[Dest:x[0-9]+]], x0, x0
147 ; CHECK: str [[Dest]], [x0]
148 define void @f8(i64 *%x) {
150 tail call void asm sideeffect "add $0, x0, x0", "=*X"(i64 *%x)