Preserves current behavior (always select Exact if known, otherwise select Constant Max).
This is the final preparation step before letting each particular computation way to decide
how exactly it should be computed. Functional improvement is coming shortly as follow-up.
Details
Details
Diff Detail
Diff Detail
Unit Tests
Unit Tests
Time | Test | |
---|---|---|
60,040 ms | x64 debian > libFuzzer.libFuzzer::minimize_crash.test |
Event Timeline
Comment Actions
After this patch, can be you please update BECountUsers handling to also cover SymbolicMaxNotTaken? I think it's still fine at this point, but when you actually start using it, this may lead to invalidation issues.
llvm/include/llvm/Analysis/ScalarEvolution.h | ||
---|---|---|
1345 | Oops :) |
Stray bool in the param name.