[DAGCombiner] Don't skip no overflow check on UMULO if the first computeKnownBits...
authorCraig Topper <craig.topper@sifive.com>
Sun, 28 Feb 2021 16:20:57 +0000 (08:20 -0800)
committerCraig Topper <craig.topper@sifive.com>
Sun, 28 Feb 2021 16:26:22 +0000 (08:26 -0800)
commitca5247bb1770a1dfa56b78303d99f1cc9a0a06ee
treeca724b9ef7b704c75c9b59a7e9f16a76a4453bad
parent1d6a6f3b0c710ccd6558644d195cf939c4995d84
[DAGCombiner] Don't skip no overflow check on UMULO if the first computeKnownBits call doesn't return any 0 bits.

Even if the first computeKnownBits call doesn't have any zero
bits it is possible the other operand has bitwidth-1 leading zero.
In that case overflow is still impossible. So always call computeKnownBits
for both operands.
llvm/lib/CodeGen/SelectionDAG/DAGCombiner.cpp
llvm/test/CodeGen/AArch64/vec_umulo.ll
llvm/test/CodeGen/X86/vec_umulo.ll