
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.
15 lines
599 B
LLVM
15 lines
599 B
LLVM
; RUN: llc < %s -mtriple=nvptx64 -mcpu=sm_20 | FileCheck %s
|
|
; RUN: %if ptxas %{ llc < %s -mtriple=nvptx64 -mcpu=sm_20 | %ptxas-verify %}
|
|
|
|
; CHECK: .visible .func (.param .align 16 .b8 func_retval0[16]) foo0(
|
|
; CHECK: .param .align 4 .b8 foo0_param_0[8]
|
|
define <4 x float> @foo0({float, float} %arg0) {
|
|
ret <4 x float> <float 1.0, float 1.0, float 1.0, float 1.0>
|
|
}
|
|
|
|
; CHECK: .visible .func (.param .align 8 .b8 func_retval0[8]) foo1(
|
|
; CHECK: .param .align 8 .b8 foo1_param_0[16]
|
|
define <2 x float> @foo1({float, float, i64} %arg0) {
|
|
ret <2 x float> <float 1.0, float 1.0>
|
|
}
|