File: 2009-07-16-InlineAsm-M-Operand.ll

package info (click to toggle)
llvm-toolchain-19 1%3A19.1.7-3~deb12u1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm-proposed-updates
  • size: 1,998,492 kB
  • sloc: cpp: 6,951,680; ansic: 1,486,157; asm: 913,598; python: 232,024; f90: 80,126; objc: 75,281; lisp: 37,276; pascal: 16,990; sh: 10,009; ml: 5,058; perl: 4,724; awk: 3,523; makefile: 3,167; javascript: 2,504; xml: 892; fortran: 664; cs: 573
file content (16 lines) | stat: -rw-r--r-- 594 bytes parent folder | download | duplicates (23) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
 
; RUN: llc < %s -mtriple=ppc32-- -verify-machineinstrs

; Machine code verifier will call isRegTiedToDefOperand() on /all/ register use
; operands.  We must make sure that the operand flag is found correctly.

; This test case is actually not specific to PowerPC, but the (imm, reg) format
; of PowerPC "m" operands trigger this bug.

define void @memory_asm_operand(i32 %a) {
  ; "m" operand will be represented as:
  ; INLINEASM fake $0, 10, %R2, 20, -4, %R1
  ; It is difficult to find the flag operand (20) when starting from %R1
  call i32 asm "lbzx $0, $1", "=r,m" (i32 %a)
  ret void
}