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.
22 lines
512 B
LLVM
22 lines
512 B
LLVM
; RUN: llc < %s -mtriple=nvptx64 -mcpu=sm_20 | FileCheck %s
|
|
; RUN: %if ptxas %{ llc < %s -mtriple=nvptx64 -mcpu=sm_20 | %ptxas-verify %}
|
|
|
|
; Make sure aggregate param types get emitted properly.
|
|
|
|
%struct.float4 = type { float, float, float, float }
|
|
|
|
; CHECK: .visible .func bar
|
|
; CHECK: .param .align 4 .b8 bar_param_0[16]
|
|
define void @bar(%struct.float4 %f) {
|
|
entry:
|
|
ret void
|
|
}
|
|
|
|
; CHECK: .visible .func foo
|
|
; CHECK: .param .align 4 .b8 foo_param_0[20]
|
|
define void @foo([5 x i32] %f) {
|
|
entry:
|
|
ret void
|
|
}
|
|
|