diff options
| author | Sanjay Patel <spatel@rotateright.com> | 2019-11-19 12:24:55 -0500 |
|---|---|---|
| committer | Sanjay Patel <spatel@rotateright.com> | 2019-11-19 14:57:35 -0500 |
| commit | 0a8e7ca402eb3470eb5faf4982581771cb849130 (patch) | |
| tree | 35faaf67616672c4138ea7c2af9e5ef36c022bf0 /lldb/packages/Python/lldbsuite/test/python_api | |
| parent | a84b48d01e3e77b754a6d4d7326e4a0c4faa10ab (diff) | |
| download | bcm5719-llvm-0a8e7ca402eb3470eb5faf4982581771cb849130.tar.gz bcm5719-llvm-0a8e7ca402eb3470eb5faf4982581771cb849130.zip | |
[SLP] fix miscompile on min/max reductions with extra uses (PR43948) (2nd try)
The 1st attempt was reverted because it revealed an existing
bug where we could produce invalid IR (use of value before
definition). That should be fixed with:
rG39de82ecc9c2
The bug manifests as replacing a reduction operand with an undef
value.
The problem appears to be limited to cases where a min/max reduction
has extra uses of the compare operand to the select.
In the general case, we are tracking "ExternallyUsedValues" and
an "IgnoreList" of the reduction operations, but those may not apply
to the final compare+select in a min/max reduction.
For that, we use replaceAllUsesWith (RAUW) to ensure that the new
vectorized reduction values are transferred to all subsequent users.
Differential Revision: https://reviews.llvm.org/D70148
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api')
0 files changed, 0 insertions, 0 deletions
