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.
21 lines
558 B
LLVM
21 lines
558 B
LLVM
; RUN: llc < %s -mtriple=nvptx64 -O2 -mcpu=sm_70 -mattr=+ptx63 | FileCheck %s
|
|
; RUN: %if ptxas %{ llc < %s -mtriple=nvptx64 -mcpu=sm_70 -mattr=+ptx63 | %ptxas-verify -arch=sm_70 %}
|
|
|
|
declare void @llvm.nvvm.nanosleep(i32)
|
|
|
|
; CHECK-LABEL: test_nanosleep_r
|
|
define void @test_nanosleep_r(i32 noundef %d) {
|
|
entry:
|
|
; CHECK: nanosleep.u32 %[[REG:.+]];
|
|
call void @llvm.nvvm.nanosleep(i32 %d)
|
|
ret void
|
|
}
|
|
|
|
; CHECK-LABEL: test_nanosleep_i
|
|
define void @test_nanosleep_i() {
|
|
entry:
|
|
; CHECK: nanosleep.u32 42;
|
|
call void @llvm.nvvm.nanosleep(i32 42)
|
|
ret void
|
|
}
|