
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.
13 lines
460 B
LLVM
13 lines
460 B
LLVM
; RUN: llc < %s -mtriple=amdgcn -mcpu=verde -verify-machineinstrs -mattr=dumpcode -filetype=obj | FileCheck --check-prefix=SI %s
|
|
; RUN: llc < %s -mtriple=amdgcn -mcpu=tonga -verify-machineinstrs -mattr=dumpcode -filetype=obj | FileCheck --check-prefix=SI %s
|
|
|
|
; Test for a crash in the custom assembly dump code.
|
|
|
|
; SI: test:
|
|
; SI: BB0_0:
|
|
; SI: s_endpgm
|
|
define amdgpu_kernel void @test(ptr addrspace(1) %out) {
|
|
store i32 0, ptr addrspace(1) %out
|
|
ret void
|
|
}
|