40a4cbb0f2
Similar to 806761a762
-mtriple= specifies the full target triple while -march= merely sets the
architecture part of the default target triple (e.g. Windows, macOS).
Therefore, -march= is error-prone and not recommended for tests without
a target triple. The issue has been benign as these MIR tests do not
utilize object file format specific detail, but it's good to change
these tests to neighbor files that use -mtriple=x86_64
25 lines
467 B
YAML
25 lines
467 B
YAML
# RUN: not llc -mtriple=x86_64 -run-pass none -o /dev/null %s 2>&1 | FileCheck %s
|
|
|
|
--- |
|
|
|
|
define i32 @test(ptr %a) {
|
|
entry:
|
|
%b = load i32, ptr %a
|
|
ret i32 %b
|
|
}
|
|
|
|
...
|
|
---
|
|
name: test
|
|
tracksRegLiveness: true
|
|
liveins:
|
|
- { reg: '$rdi' }
|
|
body: |
|
|
bb.0.entry:
|
|
liveins: $rdi
|
|
; CHECK: [[@LINE+1]]:53: expected an atomic scope, ordering or a size specification
|
|
$eax = MOV32rm killed $rdi, 1, _, 0, _ :: (load from %ir.a)
|
|
RET64 $eax
|
|
...
|
|
|