[llvm] [CostModel][X86] Attempt to match cheap v4f32 shuffles that map to SHUFPS instruction (PR #121778)
via llvm-commits
llvm-commits at lists.llvm.org
Mon Jan 6 07:43:46 PST 2025
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)' d993b11b86dcae75b582939337770eaf1c1a228b 5bf964e99ccc1766a39e4fab1118a00f875f5faa llvm/lib/Target/X86/X86TargetTransformInfo.cpp llvm/test/Analysis/CostModel/X86/alternate-shuffle-cost.ll llvm/test/Analysis/CostModel/X86/reduction.ll llvm/test/Analysis/CostModel/X86/shuffle-insert_subvector-codesize.ll llvm/test/Analysis/CostModel/X86/shuffle-insert_subvector-latency.ll llvm/test/Analysis/CostModel/X86/shuffle-insert_subvector-sizelatency.ll llvm/test/Analysis/CostModel/X86/shuffle-insert_subvector.ll llvm/test/Analysis/CostModel/X86/shuffle-splice-codesize.ll llvm/test/Analysis/CostModel/X86/shuffle-splice-latency.ll llvm/test/Analysis/CostModel/X86/shuffle-splice-sizelatency.ll llvm/test/Analysis/CostModel/X86/shuffle-splice.ll llvm/test/Transforms/PhaseOrdering/X86/hadd.ll llvm/test/Transforms/PhaseOrdering/X86/hsub.ll llvm/test/Transforms/VectorCombine/X86/shuffle-of-cmps.ll
``````````
</details>
The following files introduce new uses of undef:
- llvm/test/Analysis/CostModel/X86/shuffle-insert_subvector-codesize.ll
- llvm/test/Analysis/CostModel/X86/shuffle-insert_subvector-latency.ll
- llvm/test/Analysis/CostModel/X86/shuffle-insert_subvector-sizelatency.ll
- llvm/test/Analysis/CostModel/X86/shuffle-insert_subvector.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/121778
More information about the llvm-commits
mailing list