diff options
| author | Roman Lebedev <lebedev.ri@gmail.com> | 2022-02-16 21:57:04 +0300 |
|---|---|---|
| committer | Roman Lebedev <lebedev.ri@gmail.com> | 2022-02-16 22:16:02 +0300 |
| commit | ae48af582b34f571fdfb1a05adda0f3bc9fe5569 (patch) | |
| tree | 8bd8193ae0ece724908441d40e98c51d06c9642c /lldb/source/Plugins/ScriptInterpreter/Python/SWIGPythonBridge.h | |
| parent | 3c7d48ed902a7136a131c1288d75bfcf7af557c6 (diff) | |
| download | llvm-ae48af582b34f571fdfb1a05adda0f3bc9fe5569.zip llvm-ae48af582b34f571fdfb1a05adda0f3bc9fe5569.tar.gz llvm-ae48af582b34f571fdfb1a05adda0f3bc9fe5569.tar.bz2 | |
[NFC][SCEV] Recognize umin_seq when operand is zext'ed in zero-check
zext(umin(x,y)) == umin(zext(x),zext(y))
zext(x) == 0 -> x == 0
While it is not a very likely scenario, we probably should not expect
that instcombine already dropped such a redundant zext,
but handle directly. Moreover, perhaps there was no ZExtInst,
and SCEV somehow managed to pull out said zext out of the SCEV expression.
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/SWIGPythonBridge.h')
0 files changed, 0 insertions, 0 deletions