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() hjyamauchi on Aug 9 2017, 2:30 PM. Authored by
Details Avoid checking each operand and calling getValueFromCondition() before calling This fixes a large compile time regression in an internal build.
Diff Detail
Event Timeline
Comment Actions lgtm
|
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.