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

package info (click to toggle)
llvm-toolchain-13 1%3A13.0.1-6~deb11u1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 1,418,812 kB
  • sloc: cpp: 5,290,827; ansic: 996,570; asm: 544,593; python: 188,212; objc: 72,027; lisp: 30,291; f90: 25,395; sh: 24,900; javascript: 9,780; pascal: 9,398; perl: 7,484; ml: 5,432; awk: 3,523; makefile: 2,892; xml: 953; cs: 573; fortran: 539
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
}