diff options
| author | Max Kazantsev <mkazantsev@azul.com> | 2022-07-28 13:27:19 +0700 |
|---|---|---|
| committer | Max Kazantsev <mkazantsev@azul.com> | 2022-07-28 13:36:56 +0700 |
| commit | 2d1c6e0b4418e92df286cba428a3e4cf56d7aa2f (patch) | |
| tree | 7e3596233def926aef5ed9a9b0150dc8fabb7598 /lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.h | |
| parent | d9e02a30b16ea65a7da87913c40af03e22c9571f (diff) | |
| download | llvm-2d1c6e0b4418e92df286cba428a3e4cf56d7aa2f.zip llvm-2d1c6e0b4418e92df286cba428a3e4cf56d7aa2f.tar.gz llvm-2d1c6e0b4418e92df286cba428a3e4cf56d7aa2f.tar.bz2 | |
[LAA] Remove block order sensitivity in LAA algorithm. PR56672
As test in PR56672 shows, LAA produces different results which lead to either
positive or negative vectorization decisions depending on the order of blocks
in loop. The exact reason of this is not clear to me, however this makes investigation
of related bugs extremely complex.
Current order of blocks in the loop is arbitrary. It may change, for example, if loop
info analysis is dropped and recomputed. Seems that it interferes with LAA's logic.
This patch chooses fixed traversal order of blocks in loops, making it RPOT.
Note: this is *not* a fix for bug with incorrect analysis result. It just makes
the answer more robust to make the investigation easier.
Differential Revision: https://reviews.llvm.org/D130482
Reviewed By: aeubanks, fhahn
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.h')
0 files changed, 0 insertions, 0 deletions