This reverts commit 80a34ae311 with fixes.
Previously, since bots turning on EXPENSIVE_CHECKS are essentially turning on
MachineVerifierPass by default on X86 and the fact that
inline-asm-avx-v-constraint-32bit.ll and inline-asm-avx512vl-v-constraint-32bit.ll
are not expected to generate functioning machine code, this would go
down to `report_fatal_error` in MachineVerifierPass. Here passing
`-verify-machineinstrs=0` to make the intent explicit.
23 lines
585 B
YAML
23 lines
585 B
YAML
# RUN: not --crash llc -mtriple=thumb -run-pass none -o /dev/null %s 2>&1 | FileCheck %s
|
|
# This test ensures that the MIR parser runs the machine verifier after parsing.
|
|
|
|
--- |
|
|
|
|
define i32 @inc(i32 %a) {
|
|
entry:
|
|
ret i32 %a
|
|
}
|
|
|
|
...
|
|
---
|
|
name: inc
|
|
tracksRegLiveness: true
|
|
body: |
|
|
bb.0.entry:
|
|
; CHECK: *** Bad machine code: Unsupported register in Thumb1 push/pop ***
|
|
frame-setup tPUSH 14, $noreg, undef $r12, killed $lr, implicit-def $sp, implicit $sp
|
|
|
|
; CHECK: *** Bad machine code: Non-flag-setting Thumb1 mov is v6-only ***
|
|
$r2 = tMOVr killed $r6, 14, $noreg
|
|
...
|