These can be handled the same way as ule/ult, just using umax instead of umin. This is useful in cases where the umax prevents the upper bound from overflowing.
Details
Details
Diff Detail
Diff Detail
Unit Tests
Unit Tests
| Time | Test | |
|---|---|---|
| 660 ms | x64 windows > lld.MachO::reproduce.s |
Event Timeline
Comment Actions
LGTM, thanks!
Would it be possible to have a test which requires multiple re-writes, by limiting the IV in both directions?
| llvm/test/Analysis/ScalarEvolution/max-backedge-taken-count-guard-info.ll | ||
|---|---|---|
| 636 | IMO it would slightly increase the readability of the test here if we would use the uge predicate, as in the test name :) | |
| llvm/test/Analysis/ScalarEvolution/max-backedge-taken-count-guard-info.ll | ||
|---|---|---|
| 636 | Yeah, that makes a lot more sense :) I just picked picked the order from the original test case... | |
IMO it would slightly increase the readability of the test here if we would use the uge predicate, as in the test name :)