From 0bb9c05b1ec654eeba195c0e1a4030f795a2f09d Mon Sep 17 00:00:00 2001 From: Florian Hahn Date: Mon, 5 Jul 2021 15:56:03 +0100 Subject: [PATCH] [LV] Extend FIXME in test add in 91ee1e379901af3. --- .../LoopVectorize/runtime-check-small-clamped-bounds.ll | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/llvm/test/Transforms/LoopVectorize/runtime-check-small-clamped-bounds.ll b/llvm/test/Transforms/LoopVectorize/runtime-check-small-clamped-bounds.ll index 8875f17..0b4d1f5 100644 --- a/llvm/test/Transforms/LoopVectorize/runtime-check-small-clamped-bounds.ll +++ b/llvm/test/Transforms/LoopVectorize/runtime-check-small-clamped-bounds.ll @@ -1,10 +1,13 @@ ; NOTE: Assertions have been autogenerated by utils/update_test_checks.py ; RUN: opt -loop-vectorize -force-vector-width=2 -S %s | FileCheck %s -; Tests where the indices of some accesses are clamped to a small value. -; FIXME: At the moment, the runtime checks require that the indices do not wrap. -; The clamped indices do wrap, so the vector loops are dead at the -; moment. +; Tests where the indices of some accesses are clamped to a small range. + +; FIXME: At the moment, the runtime checks require that the indices do not wrap +; and runtime checks are emitted to ensure that. The clamped indices do +; wrap, so the vector loops are dead at the moment. But it is still +; possible to compute the bounds of the accesses and generate proper +; runtime checks. ; The relevant bounds for %gep.A are [%A, %A+4). define void @load_clamped_index(i32* %A, i32* %B, i32 %N) { -- 2.7.4