40a4cbb0f2
Similar to 806761a7629df268c8aed49657aeccffa6bca449 -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
26 lines
542 B
YAML
26 lines
542 B
YAML
# RUN: not llc -mtriple=x86_64 -run-pass none -o /dev/null %s 2>&1 | FileCheck %s
|
|
# This test ensures that the MIR parser reports an error when parsing an invalid
|
|
# constant value.
|
|
|
|
--- |
|
|
|
|
define double @test(double %a, float %b) {
|
|
entry:
|
|
%c = fadd double %a, 3.250000e+00
|
|
ret double %c
|
|
}
|
|
|
|
...
|
|
---
|
|
name: test
|
|
constants:
|
|
- id: 0
|
|
# CHECK: [[@LINE+1]]:19: expected type
|
|
value: 'dub 3.250000e+00'
|
|
body: |
|
|
bb.0.entry:
|
|
%xmm0 = ADDSDrm killed %xmm0, %rip, 1, _, %const.0, _
|
|
RET64 %xmm0
|
|
...
|
|
|