806761a762
The issue is uncovered by #47698: for IR files without a target triple, -mtriple= specifies the full target triple while -march= merely sets the architecture part of the default target triple, leaving a target triple which may not make sense, e.g. riscv64-apple-darwin. Therefore, -march= is error-prone and not recommended for tests without a target triple. The issue has been benign as we recognize $unknown-apple-darwin as ELF instead of rejecting it outrightly.
22 lines
780 B
LLVM
22 lines
780 B
LLVM
; RUN: llc -mtriple=amdgcn -mtriple=amdgcn-- -mcpu=unknown -verify-machineinstrs < %s 2>&1 | FileCheck -check-prefix=ERROR -check-prefix=GCN %s
|
|
; RUN: llc -march=r600 -mtriple=r600-- -mcpu=unknown -verify-machineinstrs < %s 2>&1 | FileCheck -check-prefix=ERROR -check-prefix=R600 %s
|
|
target datalayout = "A5"
|
|
|
|
; Should not crash when the processor is not recognized and the
|
|
; wavefront size feature not set.
|
|
|
|
; Should also not have fragments of r600 and gcn isa mixed.
|
|
|
|
; ERROR: 'unknown' is not a recognized processor for this target (ignoring processor)
|
|
|
|
; GCN-NOT: MOV
|
|
; GCN: buffer_store_dword
|
|
; GCN: ScratchSize: 8{{$}}
|
|
|
|
; R600: MOV
|
|
define amdgpu_kernel void @foo() {
|
|
%alloca = alloca i32, align 4, addrspace(5)
|
|
store volatile i32 0, ptr addrspace(5) %alloca
|
|
ret void
|
|
}
|