xref: /aosp_15_r20/external/llvm/test/CodeGen/PowerPC/2009-07-16-InlineAsm-M-Operand.ll (revision 9880d6810fe72a1726cb53787c6711e909410d58)
1*9880d681SAndroid Build Coastguard Worker; RUN: llc < %s -march=ppc32 -verify-machineinstrs
2*9880d681SAndroid Build Coastguard Worker
3*9880d681SAndroid Build Coastguard Worker; Machine code verifier will call isRegTiedToDefOperand() on /all/ register use
4*9880d681SAndroid Build Coastguard Worker; operands.  We must make sure that the operand flag is found correctly.
5*9880d681SAndroid Build Coastguard Worker
6*9880d681SAndroid Build Coastguard Worker; This test case is actually not specific to PowerPC, but the (imm, reg) format
7*9880d681SAndroid Build Coastguard Worker; of PowerPC "m" operands trigger this bug.
8*9880d681SAndroid Build Coastguard Worker
9*9880d681SAndroid Build Coastguard Workerdefine void @memory_asm_operand(i32 %a) {
10*9880d681SAndroid Build Coastguard Worker  ; "m" operand will be represented as:
11*9880d681SAndroid Build Coastguard Worker  ; INLINEASM <es:fake $0>, 10, %R2, 20, -4, %R1
12*9880d681SAndroid Build Coastguard Worker  ; It is difficult to find the flag operand (20) when starting from %R1
13*9880d681SAndroid Build Coastguard Worker  call i32 asm "lbzx $0, $1", "=r,m" (i32 %a)
14*9880d681SAndroid Build Coastguard Worker  ret void
15*9880d681SAndroid Build Coastguard Worker}
16*9880d681SAndroid Build Coastguard Worker
17