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.
15 lines
622 B
LLVM
15 lines
622 B
LLVM
; RUN: llc < %s -O0 -mtriple=nvptx64 -mcpu=sm_20 | FileCheck %s
|
|
; RUN: %if ptxas %{ llc < %s -O0 -mtriple=nvptx64 -mcpu=sm_20 | %ptxas-verify %}
|
|
|
|
; CHECK-LABEL: .visible .func (.param .align 16 .b8 func_retval0[32]) foo(
|
|
define { i128, i128 } @foo(i64 %a, i32 %b) {
|
|
%1 = sext i64 %a to i128
|
|
%2 = sext i32 %b to i128
|
|
%3 = insertvalue { i128, i128 } undef, i128 %1, 0
|
|
%4 = insertvalue { i128, i128 } %3, i128 %2, 1
|
|
|
|
; CHECK: st.param.v2.b64 [func_retval0], {%[[REG1:rd[0-9]+]], %[[REG2:rd[0-9]+]]};
|
|
; CHECK: st.param.v2.b64 [func_retval0+16], {%[[REG3:rd[0-9]+]], %[[REG4:rd[0-9]+]]};
|
|
ret { i128, i128 } %4
|
|
}
|