Instead of rolling our own min/max matching code (which is notoriously hard to get completely right), use ValueTracking's instead.
MFCI (minimal functional change intended)
Differential D13029
[PatternMatch] Switch to using ValueTracking::matchSelectPattern for min/max matching jmolloy on Sep 21 2015, 12:39 PM. Authored by
Details
Diff Detail
Event Timeline
Comment Actions Hi Hal, Thanks for the review.
Comment Actions Remove the redundant check as noted, and this LGTM.
|
Unless I'm mistaken, isn't this what llvm::matchSelectPattern already does? I'd be surprised if the extra call frame matters here.