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.
15 lines
518 B
LLVM
15 lines
518 B
LLVM
; RUN: llc < %s -mtriple=nvptx64 -mcpu=sm_35 | FileCheck %s
|
|
; RUN: %if ptxas %{ llc < %s -mtriple=nvptx64 -mcpu=sm_35 | %ptxas-verify %}
|
|
|
|
define void @foo(ptr nocapture readonly %x_value, ptr nocapture %output) #0 {
|
|
%1 = load <4 x float>, ptr %x_value, align 16
|
|
%2 = fpext <4 x float> %1 to <4 x double>
|
|
; CHECK-NOT: ld.v2.f32 {%fd{{[0-9]+}}, %fd{{[0-9]+}}}, [%rd{{[0-9]+}}];
|
|
; CHECK: cvt.f64.f32
|
|
; CHECK: cvt.f64.f32
|
|
; CHECK: cvt.f64.f32
|
|
; CHECK: cvt.f64.f32
|
|
store <4 x double> %2, ptr %output
|
|
ret void
|
|
}
|