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.
26 lines
835 B
LLVM
26 lines
835 B
LLVM
; RUN: llc < %s -mtriple=nvptx64 -verify-machineinstrs
|
|
; RUN: %if ptxas %{ llc < %s -mtriple=nvptx64 | %ptxas-verify %}
|
|
|
|
; Check that llc will not crash even when first MBB doesn't contain
|
|
; any instruction.
|
|
|
|
target datalayout = "e-i64:64-i128:128-v16:16-v32:32-n16:32:64"
|
|
target triple = "nvptx64"
|
|
|
|
%printf_args.0.8 = type { ptr }
|
|
|
|
define internal i32 @__kmpc_get_hardware_thread_id_in_block(i1 %0) {
|
|
%2 = alloca %printf_args.0.8, i32 0, align 8
|
|
br i1 true, label %._crit_edge1, label %._crit_edge
|
|
|
|
._crit_edge: ; preds = %1, %._crit_edge
|
|
%3 = call i32 null(ptr null, ptr %2)
|
|
br i1 %0, label %._crit_edge, label %._crit_edge1
|
|
|
|
._crit_edge1: ; preds = %._crit_edge, %1
|
|
ret i32 0
|
|
|
|
; uselistorder directives
|
|
uselistorder label %._crit_edge, { 1, 0 }
|
|
}
|