b279f6b098
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),
leaving a target triple which may not make sense.
Therefore, -march= is error-prone and not recommended for tests without
a target triple. The issue has been benign as we recognize
nvptx{,64}-apple-darwin as ELF instead of rejecting it outrightly.
14 lines
360 B
LLVM
14 lines
360 B
LLVM
; RUN: llc < %s -mtriple=nvptx64 -mcpu=sm_20 -O0 | FileCheck %s
|
|
; RUN: %if ptxas %{ llc < %s -mtriple=nvptx64 -mcpu=sm_20 -O0 | %ptxas-verify %}
|
|
|
|
define void @foo(ptr %output) {
|
|
; CHECK-LABEL: .visible .func foo(
|
|
entry:
|
|
%local = alloca i32
|
|
; CHECK: __local_depot
|
|
store i32 1, ptr %local
|
|
%0 = load i32, ptr %local
|
|
store i32 %0, ptr %output
|
|
ret void
|
|
}
|