Files
clang-p2996/llvm/test/CodeGen/VE/Vector/vec_reduce_add.ll
Fangrui Song 5240e0b891 [VE,test] Change llc -march= to -mtriple=
Similar to 806761a762

-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 $ve-apple-darwin as ELF instead
of rejecting it outrightly.
2024-12-15 10:24:14 -08:00

36 lines
1.2 KiB
LLVM

; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py
; RUN: llc < %s -O0 --mtriple=ve -mattr=+vpu | FileCheck %s
declare i64 @llvm.vector.reduce.add.v256i64(<256 x i64>)
define fastcc i64 @vec_reduce_add_v256i64(<256 x i64> %v) {
; CHECK-LABEL: vec_reduce_add_v256i64:
; CHECK: # %bb.0:
; CHECK-NEXT: lea %s0, 256
; CHECK-NEXT: # kill: def $sw0 killed $sw0 killed $sx0
; CHECK-NEXT: lvl %s0
; CHECK-NEXT: vsum.l %v0, %v0
; CHECK-NEXT: lvs %s0, %v0(0)
; CHECK-NEXT: b.l.t (, %s10)
%r = call i64 @llvm.vector.reduce.add.v256i64( <256 x i64> %v)
ret i64 %r
}
declare i32 @llvm.vector.reduce.add.v256i32(<256 x i32>)
define fastcc i32 @vec_reduce_add_v256i32(<256 x i32> %v) {
; CHECK-LABEL: vec_reduce_add_v256i32:
; CHECK: # %bb.0:
; CHECK-NEXT: lea %s0, 256
; CHECK-NEXT: # kill: def $sw0 killed $sw0 killed $sx0
; CHECK-NEXT: lvl %s0
; CHECK-NEXT: vsum.w.sx %v0, %v0
; CHECK-NEXT: lvs %s0, %v0(0)
; CHECK-NEXT: or %s1, 0, %s0
; CHECK-NEXT: # implicit-def: $sx0
; CHECK-NEXT: or %s0, 0, %s1
; CHECK-NEXT: b.l.t (, %s10)
%r = call i32 @llvm.vector.reduce.add.v256i32( <256 x i32> %v)
ret i32 %r
}