[llvm] [LoopVectorize] Refine runtime memory check costs when there is an outer loop (PR #76034)

Rin Dobrescu via llvm-commits llvm-commits at lists.llvm.org
Wed Dec 20 02:28:08 PST 2023


================
@@ -0,0 +1,193 @@
+; RUN: opt -p loop-vectorize -mattr=+sve -debug-only=loop-vectorize -S -disable-output < %s 2>&1 | FileCheck %s
+
+target datalayout = "e-m:e-i8:8:32-i16:16:32-i64:64-i128:128-n32:64-S128"
+target triple = "aarch64-unknown-linux-gnu"
+
+
+define void @outer_no_tc(ptr nocapture noundef %a, ptr nocapture noundef readonly %b, i64 noundef %m, i64 noundef %n) vscale_range(1,16) {
----------------
Rin18 wrote:

Is the `vscale_range(1, 16)` needed here (and for the other tests)? I don't think it makes any difference to the output.

https://github.com/llvm/llvm-project/pull/76034


More information about the llvm-commits mailing list