mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2025-02-01 05:01:59 +01:00
b3a8585bc1
`llc -march` is problematic because it only switches the target architecture, but leaves the operating system unchanged. This occasionally leads to indeterministic tests because the OS from LLVM_DEFAULT_TARGET_TRIPLE is used. However we can simply always use `llc -mtriple` instead. This changes all the tests to do this to avoid people using -march when they copy and paste parts of tests. This patch: - Removes -march if the .ll file already has a matching `target triple` directive or -mtriple argument. - In all other cases changes -march=ppc32/-march=ppc64 to -mtriple=ppc32--/-mtriple=ppc64-- See also the discussion in https://reviews.llvm.org/D35287 llvm-svn: 309754
17 lines
599 B
LLVM
17 lines
599 B
LLVM
; 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 <es: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
|
|
}
|
|
|