[llvm] [delinearize] use update_analyze_test_checks.py in delinearization testcases (PR #153831)

[via llvm-commits]

github-actions[bot] wrote:

<!--LLVM CODE FORMAT COMMENT: {undef deprecator}-->


:warning: undef deprecator found issues in your code. :warning:

<details>
<summary>
You can test this locally with the following command:
</summary>

``````````bash
git diff -U0 --pickaxe-regex -S '([^a-zA-Z0-9#_-]undef[^a-zA-Z0-9_-]|UndefValue::get)' 'HEAD~1' HEAD llvm/lib/Analysis/Delinearization.cpp llvm/test/Analysis/Delinearization/a.ll llvm/test/Analysis/Delinearization/byte_offset.ll llvm/test/Analysis/Delinearization/constant_functions_multi_dim.ll llvm/test/Analysis/Delinearization/divide_by_one.ll llvm/test/Analysis/Delinearization/fixed_size_array.ll llvm/test/Analysis/Delinearization/gcd_multiply_expr.ll llvm/test/Analysis/Delinearization/himeno_1.ll llvm/test/Analysis/Delinearization/himeno_2.ll llvm/test/Analysis/Delinearization/iv_times_constant_in_subscript.ll llvm/test/Analysis/Delinearization/multidim_ivs_and_integer_offsets_3d.ll llvm/test/Analysis/Delinearization/multidim_ivs_and_integer_offsets_nts_3d.ll llvm/test/Analysis/Delinearization/multidim_ivs_and_parameteric_offsets_3d.ll llvm/test/Analysis/Delinearization/multidim_only_ivs_2d.ll llvm/test/Analysis/Delinearization/multidim_only_ivs_2d_nested.ll llvm/test/Analysis/Delinearization/multidim_only_ivs_3d.ll llvm/test/Analysis/Delinearization/multidim_only_ivs_3d_cast.ll llvm/test/Analysis/Delinearization/multidim_two_accesses_different_delinearization.ll llvm/test/Analysis/Delinearization/parameter_addrec_product.ll llvm/test/Analysis/Delinearization/terms_with_identity_factor.ll llvm/test/Analysis/Delinearization/type_mismatch.ll llvm/test/Analysis/Delinearization/undef.ll
``````````

</details>


The following files introduce new uses of undef:
 - llvm/test/Analysis/Delinearization/type_mismatch.ll
 - llvm/test/Analysis/Delinearization/undef.ll

[Undef](https://llvm.org/docs/LangRef.html#undefined-values) is now deprecated and should only be used in the rare cases where no replacement is possible. For example, a load of uninitialized memory yields `undef`. You should use `poison` values for placeholders instead.

In tests, avoid using `undef` and having tests that trigger undefined behavior. If you need an operand with some unimportant value, you can add a new argument to the function and use that instead.

For example, this is considered a bad practice:
```llvm
define void @fn() {
  ...
  br i1 undef, ...
}
```

Please use the following instead:
```llvm
define void @fn(i1 %cond) {
  ...
  br i1 %cond, ...
}
```

Please refer to the [Undefined Behavior Manual](https://llvm.org/docs/UndefinedBehavior.html) for more information.



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