Skip to content

Commit 723de7f

Browse files
committed
[LV][RISCV] Try fixing Windows buildbot failure in force-vect-msg.ll. NFC
The clang-x64-windows-msvc buildbot is failing after 7074471 due to this test failing: https://lab.llvm.org/buildbot/#/builders/63/builds/8528 This is a stab in the dark, but my first thought is that it may be due to the handling of floats with MSVC or something. So this removes the floating point part of the check. I don't have access to a Windows machine handy to debug this just yet, so pushing this to see if it can quickly return the buildbot to green.
1 parent b9fef09 commit 723de7f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

llvm/test/Transforms/LoopVectorize/RISCV/force-vect-msg.ll

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
; CHECK: LV: Loop hints: force=enabled
55
; CHECK: LV: Scalar loop costs: 4.
66
; ChosenFactor.Cost is 9, but the real cost will be divided by the width, which is 2.2.
7-
; CHECK: Cost for VF vscale x 2: 9 (Estimated cost per lane: 2.2)
7+
; CHECK: Cost for VF vscale x 2: 9
88
; Regardless of force vectorization or not, this loop will eventually be vectorized because of the cost model.
99
; Therefore, the following message does not need to be printed even if vectorization is explicitly forced in the metadata.
1010
; CHECK-NOT: LV: Vectorization seems to be not beneficial, but was forced by a user.

0 commit comments

Comments
 (0)