Re: [PATCH][RFC] tree-optimization/88540 - FP x > y ? x : y if-conversion without -ffast-math

2023-07-17 Thread Andrew Pinski via Gcc-patches
On Mon, Jul 17, 2023 at 2:30 AM Richard Biener wrote: > > On Fri, 14 Jul 2023, Andrew Pinski wrote: > > > On Thu, Jul 13, 2023 at 2:54?AM Richard Biener via Gcc-patches > > wrote: > > > > > > The following makes sure that FP x > y ? x : y style max/min operations > > > are if-converted at the

Re: [PATCH][RFC] tree-optimization/88540 - FP x > y ? x : y if-conversion without -ffast-math

2023-07-17 Thread Richard Biener via Gcc-patches
On Fri, 14 Jul 2023, Andrew Pinski wrote: > On Thu, Jul 13, 2023 at 2:54?AM Richard Biener via Gcc-patches > wrote: > > > > The following makes sure that FP x > y ? x : y style max/min operations > > are if-converted at the GIMPLE level. While we can neither match > > it to MAX_EXPR nor .FMAX

Re: [PATCH][RFC] tree-optimization/88540 - FP x > y ? x : y if-conversion without -ffast-math

2023-07-14 Thread Andrew Pinski via Gcc-patches
On Thu, Jul 13, 2023 at 2:54 AM Richard Biener via Gcc-patches wrote: > > The following makes sure that FP x > y ? x : y style max/min operations > are if-converted at the GIMPLE level. While we can neither match > it to MAX_EXPR nor .FMAX as both have different semantics with IEEE > than the

[PATCH][RFC] tree-optimization/88540 - FP x > y ? x : y if-conversion without -ffast-math

2023-07-13 Thread Richard Biener via Gcc-patches
The following makes sure that FP x > y ? x : y style max/min operations are if-converted at the GIMPLE level. While we can neither match it to MAX_EXPR nor .FMAX as both have different semantics with IEEE than the ternary ?: operation we can make sure to maintain this form as a COND_EXPR so