llvm-project/llvm/test/CodeGen/X86/inline-asm-duplicated-const...

; RUN: llc < %s -no-integrated-as -mtriple=x86_64-linux-gnu | FileCheck %s

; CHECK-LABEL: test1:
; CHECK: movl	(%rdi), %eax
; CHECK: nop
; CHECK: movl	%eax, (%rdi)
; CHECK: ret
define void @test1(i32* %l) {
  %load = load i32, i32* %l
  call void asm "nop", "=*rmrm,0m0m,~{dirflag},~{fpsr},~{flags}"(i32* %l, i32 %load)
  ret void
}
X86: Do not use llc -march in tests. `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. See also the discussion in https://reviews.llvm.org/D35287 llvm-svn: 309774 2017-08-02 08:28:10 +08:00			`; RUN: llc < %s -no-integrated-as -mtriple=x86_64-linux-gnu \| FileCheck %s`
[inline asm] Don't reject duplicated matching constraints They're harmless and it's easy to generate them from clang, leading to a crash in LLVM. Found by afl-fuzz. llvm-svn: 233500 2015-03-30 04:33:07 +08:00
			`; CHECK-LABEL: test1:`
			`; CHECK: movl (%rdi), %eax`
			`; CHECK: nop`
			`; CHECK: movl %eax, (%rdi)`
			`; CHECK: ret`
			`define void @test1(i32* %l) {`
			`%load = load i32, i32* %l`
			`call void asm "nop", "=rmrm,0m0m,~{dirflag},~{fpsr},~{flags}"(i32 %l, i32 %load)`
			`ret void`
			`}`