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.
25 lines
503 B
LLVM
25 lines
503 B
LLVM
; RUN: llc < %s -mtriple=nvptx64 2>&1 | FileCheck %s
|
|
; RUN: %if ptxas %{ llc < %s -mtriple=nvptx64 | %ptxas-verify %}
|
|
|
|
; Make sure the example doesn't crash with segfault
|
|
|
|
; CHECK: .visible .func ({{.*}}) loop
|
|
define i32 @loop(i32, i32) {
|
|
entry:
|
|
br label %loop
|
|
|
|
loop:
|
|
%i = phi i32 [ %0, %entry ], [ %res, %loop ]
|
|
%res = call i32 @div(i32 %i, i32 %1)
|
|
|
|
%exitcond = icmp eq i32 %res, %0
|
|
br i1 %exitcond, label %exit, label %loop
|
|
|
|
exit:
|
|
ret i32 %res
|
|
}
|
|
|
|
define i32 @div(i32, i32) {
|
|
ret i32 0
|
|
}
|