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
30 lines
579 B
YAML
30 lines
579 B
YAML
# RUN: not llc -mtriple=x86_64 -run-pass none -o /dev/null %s 2>&1 | FileCheck %s
|
|
--- |
|
|
|
|
define i32 @test(i32 %a) {
|
|
entry:
|
|
%b = alloca i32
|
|
store i32 %a, ptr %b
|
|
%c = load i32, ptr %b
|
|
ret i32 %c
|
|
}
|
|
|
|
...
|
|
---
|
|
name: test
|
|
tracksRegLiveness: true
|
|
registers:
|
|
- { id: 0, class: gr32 }
|
|
frameInfo:
|
|
maxAlignment: 4
|
|
stack:
|
|
- { id: 0, name: b, size: 4, alignment: 4 }
|
|
body: |
|
|
bb.0.entry:
|
|
%0 = COPY $edi
|
|
; CHECK: [[@LINE+1]]:13: use of undefined stack object '%stack.2'
|
|
MOV32mr %stack.2, 1, _, 0, _, %0
|
|
$eax = COPY %0
|
|
RET64 $eax
|
|
...
|