[llvm] [TLI][NFC] Autogenerate vectorized call tests for SLEEF/ArmPL. (PR #76146)

[Maciej Gabka via llvm-commits]

================
@@ -0,0 +1,2639 @@
+; NOTE: Assertions have been autogenerated by utils/update_test_checks.py UTC_ARGS: --filter "call.*(cos|sin|tan|cbrt|erf|exp|gamma|log|sqrt|copysign|dim|min|mod|hypot|nextafter|pow|fma)" --version 2
+; RUN: opt -mattr=+neon -vector-library=sleefgnuabi -passes=inject-tli-mappings,loop-vectorize,simplifycfg -force-vector-interleave=1 -S < %s | FileCheck %s --check-prefix=SLEEF-NEON
+; RUN: opt -mattr=+sve -vector-library=sleefgnuabi -passes=inject-tli-mappings,loop-vectorize,simplifycfg -force-vector-interleave=1 -prefer-predicate-over-epilogue=predicate-dont-vectorize -S < %s | FileCheck %s --check-prefix=SLEEF-SVE
+; RUN: opt -mattr=+neon -vector-library=ArmPL -passes=inject-tli-mappings,loop-vectorize,simplifycfg -force-vector-interleave=1 -S < %s | FileCheck %s --check-prefix=ARMPL-NEON
+; RUN: opt -mattr=+sve -vector-library=ArmPL -passes=inject-tli-mappings,loop-vectorize,simplifycfg -force-vector-interleave=1 -prefer-predicate-over-epilogue=predicate-dont-vectorize -S < %s | FileCheck %s --check-prefix=ARMPL-SVE
+
+target triple = "aarch64-unknown-linux-gnu"
+
+; Tests are checking if LV can vectorize loops with library calls
----------------
mgabka wrote:

I think it would be good to be more specific here, what about:
"Tests are checking if LV can vectorize loops with function calls for which compiler provides mappings to their vector variants via TLI. Tests are checking fixed with vectorization with neon and scalable vectorization with sve."

May I also suggest changing the test file nam to maybe veclib-function-calls.ll
and the other to be veclib-intrinsic-calls.ll

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