2208c97c1b
Similar to 806761a7629df268c8aed49657aeccffa6bca449 -mtriple= specifies the full target triple while -march= merely sets the architecture part of the default target triple, 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 $unknown-apple-darwin as ELF instead of rejecting it outrightly.
33 lines
1.3 KiB
LLVM
33 lines
1.3 KiB
LLVM
; RUN: llc -mtriple=hexagon < %s | FileCheck %s
|
|
; Check that we generate a hardware loop instruction.
|
|
; CHECK: endloop0
|
|
|
|
@A = common global [400 x i8] zeroinitializer, align 8
|
|
@B = common global [400 x i8] zeroinitializer, align 8
|
|
@C = common global [400 x i8] zeroinitializer, align 8
|
|
|
|
define void @run() nounwind {
|
|
entry:
|
|
br label %polly.loop_body
|
|
|
|
polly.loop_after: ; preds = %polly.loop_body
|
|
ret void
|
|
|
|
polly.loop_body: ; preds = %entry, %polly.loop_body
|
|
%polly.loopiv16 = phi i32 [ 0, %entry ], [ %polly.next_loopiv, %polly.loop_body ]
|
|
%polly.next_loopiv = add i32 %polly.loopiv16, 4
|
|
%p_vector_iv14 = or i32 %polly.loopiv16, 1
|
|
%p_vector_iv3 = add i32 %p_vector_iv14, 1
|
|
%p_vector_iv415 = or i32 %polly.loopiv16, 3
|
|
%p_arrayidx = getelementptr [400 x i8], ptr @A, i32 0, i32 %polly.loopiv16
|
|
%p_arrayidx5 = getelementptr [400 x i8], ptr @A, i32 0, i32 %p_vector_iv14
|
|
%p_arrayidx6 = getelementptr [400 x i8], ptr @A, i32 0, i32 %p_vector_iv3
|
|
%p_arrayidx7 = getelementptr [400 x i8], ptr @A, i32 0, i32 %p_vector_iv415
|
|
store i8 123, ptr %p_arrayidx, align 1
|
|
store i8 123, ptr %p_arrayidx5, align 1
|
|
store i8 123, ptr %p_arrayidx6, align 1
|
|
store i8 123, ptr %p_arrayidx7, align 1
|
|
%0 = icmp slt i32 %polly.next_loopiv, 400
|
|
br i1 %0, label %polly.loop_body, label %polly.loop_after
|
|
}
|