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.
17 lines
655 B
LLVM
17 lines
655 B
LLVM
; RUN: llc < %s -mtriple=nvptx64 -mcpu=sm_90a -mattr=+ptx80| FileCheck --check-prefixes=CHECK %s
|
|
; RUN: %if ptxas-12.0 %{ llc < %s -mtriple=nvptx64 -mcpu=sm_90a -mattr=+ptx80| %ptxas-verify -arch=sm_90a %}
|
|
|
|
declare void @llvm.nvvm.setmaxnreg.inc.sync.aligned.u32(i32 %reg_count)
|
|
declare void @llvm.nvvm.setmaxnreg.dec.sync.aligned.u32(i32 %reg_count)
|
|
|
|
; CHECK-LABEL: test_set_maxn_reg
|
|
define void @test_set_maxn_reg() {
|
|
; CHECK: setmaxnreg.inc.sync.aligned.u32 96;
|
|
call void @llvm.nvvm.setmaxnreg.inc.sync.aligned.u32(i32 96)
|
|
|
|
; CHECK: setmaxnreg.dec.sync.aligned.u32 64;
|
|
call void @llvm.nvvm.setmaxnreg.dec.sync.aligned.u32(i32 64)
|
|
|
|
ret void
|
|
}
|