b279f6b098
Similar to 806761a762
-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.
21 lines
668 B
LLVM
21 lines
668 B
LLVM
; RUN: llc < %s -mtriple=nvptx64 -mcpu=sm_20 | FileCheck %s
|
|
; RUN: %if ptxas %{ llc < %s -mtriple=nvptx64 -mcpu=sm_20 | %ptxas-verify %}
|
|
|
|
target datalayout = "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v16:16:16-v32:32:32-v64:64:64-v128:128:128-n16:32:64"
|
|
target triple = "nvptx-nvidia-cuda"
|
|
|
|
; Make sure predicate (i1) operands to kernels get expanded out to .u8
|
|
|
|
; CHECK: .entry foo
|
|
; CHECK: .param .u8 foo_param_0
|
|
; CHECK: .param .u64 .ptr .align 1 foo_param_1
|
|
define void @foo(i1 %p, ptr %out) {
|
|
%val = zext i1 %p to i32
|
|
store i32 %val, ptr %out
|
|
ret void
|
|
}
|
|
|
|
|
|
!nvvm.annotations = !{!0}
|
|
!0 = !{ptr @foo, !"kernel", i32 1}
|