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)'
18886b32730eb5a282cae7230802cc413ed22920
c49bc4714589cf548a6382ea5a99f31626d3d6a2
llvm/test/CodeGen/DirectX/BufferStore-sm61.ll
llvm/test/CodeGen/DirectX/RawBufferStore-error64.ll
llvm/test/CodeGen/DirectX/RawBufferStore.ll
llvm/lib/Target/DirectX/DXILOpLowering.cpp
``````````
</details>
The following files introduce new uses of undef:
- llvm/lib/Target/DirectX/DXILOpLowering.cpp
- llvm/test/CodeGen/DirectX/BufferStore-sm61.ll
- llvm/test/CodeGen/DirectX/RawBufferStore.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/121282
_______________________________________________
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
