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
36 lines
715 B
YAML
36 lines
715 B
YAML
# RUN: not llc -mtriple=x86_64 -run-pass none -o /dev/null %s 2>&1 | FileCheck %s
|
|
# This test ensures that an error is reported when an unknown named machine
|
|
# basic block is encountered.
|
|
|
|
--- |
|
|
|
|
define i32 @foo(ptr %p) {
|
|
entry:
|
|
%a = load i32, ptr %p
|
|
%0 = icmp sle i32 %a, 10
|
|
br i1 %0, label %less, label %exit
|
|
|
|
less:
|
|
ret i32 0
|
|
|
|
exit:
|
|
ret i32 %a
|
|
}
|
|
|
|
...
|
|
---
|
|
name: foo
|
|
body: |
|
|
bb.0.entry:
|
|
$eax = MOV32rm $rdi, 1, _, 0, _
|
|
CMP32ri8 $eax, 10, implicit-def $eflags
|
|
; CHECK: [[@LINE+1]]:11: the name of machine basic block #2 isn't 'hit'
|
|
JCC_1 %bb.2.hit, 15, implicit $eflags
|
|
|
|
bb.1.less:
|
|
$eax = MOV32r0 implicit-def $eflags
|
|
|
|
bb.2.exit:
|
|
RET64 $eax
|
|
...
|