Avoid checking each operand and calling getValueFromCondition() before calling
constantFoldUser() when the instruction type isn't supported by
constantFoldUser().
This fixes a large compile time regression in an internal build.
Differential D36552
[LVI] Fix LVI compile time regression around constantFoldUser() ClosedPublic Authored by hjyamauchi on Aug 9 2017, 2:30 PM.
Details Summary Avoid checking each operand and calling getValueFromCondition() before calling This fixes a large compile time regression in an internal build.
Diff Detail
Event Timelinesanjoy added inline comments. This revision now requires changes to proceed.Aug 9 2017, 2:52 PM hjyamauchi edited edge metadata. hjyamauchi marked 2 inline comments as done. Comment ActionsAddressed comments.
Comment Actions lgtm
This revision is now accepted and ready to land.Aug 9 2017, 6:33 PM
Revision Contents
Diff 110488 lib/Analysis/LazyValueInfo.cpp
|
I'd call this isOperationFoldable since we're not checking if Usr is foldable or not but only looking at its operation to see if it could possibly be constant folded.