Re: [PATCH] Improve merge_ranges (PR tree-optimization/69615)

2018-06-03 Thread Richard Biener
On Sun, 3 Jun 2018, Jakub Jelinek wrote: > Hi! > > We canonicalize x < type_max_val (type (x)) as x != type_max_val (type (x)) > and similarly for x > type_min_val (type (x)). Unfortunately the former > form is what is often more beneficial for merge_ranges, if we have as in the > testcase e.g.

[PATCH] Improve merge_ranges (PR tree-optimization/69615)

2018-06-03 Thread Jakub Jelinek
Hi! We canonicalize x < type_max_val (type (x)) as x != type_max_val (type (x)) and similarly for x > type_min_val (type (x)). Unfortunately the former form is what is often more beneficial for merge_ranges, if we have as in the testcase e.g. x >= 0 && x != __INT_MAX__, in?_p is different and we