Fix two bugs in SelectionDAGBuilder::FindMergedConditions reported by
Mikael Holmen. Handle non-canonicalized xor not operation
correctly (was assuming operand 0 was always the non-constant operand)
and check that the negated condition is also in the same block as the
original and/or instruction (as is done for and/or operands already)
before proceeding with optimization.
Details
Details
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
Comment Actions
Are there PRs for the reported bugs, or where were they reported? I'm trying to understand whether this is fixing a regression from 3.9 or not.
Comment Actions
@hans Sorry for the noise, but I just checked and these bugs were introduced after the release_40 branch, so you can ignore my request to include this patch.
Comment Actions
I'm going to go ahead and check this in as an obvious fix since it fixes breakages for at least two targets.