maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/MachineVerifier/test_g_merge_values.mir

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

29 lines
853 B
Plaintext
Raw Normal View History

Revert "Revert "Reland "[Support] make report_fatal_error `abort` instead of `exit`""" This reverts commit 80a34ae31125aa46dcad47162ba45b152aed968d 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.
2020-02-12 15:01:35 +08:00
# RUN: not --crash llc -o - -march=arm64 -run-pass=none -verify-machineinstrs %s 2>&1 | FileCheck %s
GlobalISel: Verify G_MERGE_VALUES operand sizes llvm-svn: 364822
2019-07-02 02:01:35 +08:00
# REQUIRES: aarch64-registered-target
---
name: g_merge_values
tracksRegLiveness: true
liveins:
body: |
bb.0:
%0:_(s32) = IMPLICIT_DEF
%1:_(s32) = IMPLICIT_DEF
%2:_(<2 x s32>) = IMPLICIT_DEF
%3:_(<2 x s32>) = IMPLICIT_DEF
; CHECK: Bad machine code: G_MERGE_VALUES cannot operate on vectors
%4:_(<4 x s32>) = G_MERGE_VALUES %2, %3
; CHECK: Bad machine code: G_MERGE_VALUES result size is inconsistent
%5:_(s64) = G_MERGE_VALUES %0
; CHECK: Bad machine code: G_MERGE_VALUES result size is inconsistent
%6:_(s64) = G_MERGE_VALUES %0, %1, %1
%7:_(s16) = IMPLICIT_DEF
; CHECK: Bad machine code: G_MERGE_VALUES source types do not match
%8:_(s64) = G_MERGE_VALUES %0, %7
...