[Bug tree-optimization/113379] `MIN == MAX` should be optimzed to `a == b`

[jsm28 at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113379

--- Comment #2 from Joseph S. Myers  ---
Note that some of these aren't valid for floating point in the presence of
NaNs.

[Bug tree-optimization/113379] `MIN == MAX` should be optimzed to `a == b`

[rguenth at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113379

Richard Biener  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2024-01-15
 Ever confirmed|0   |1

[Bug tree-optimization/113379] `MIN == MAX` should be optimzed to `a == b`

[pinskia at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113379

Andrew Pinski  changed:

   What|Removed |Added

   Severity|normal  |enhancement

--- Comment #1 from Andrew Pinski  ---
The rest of the comparison operators:

`MIN  <= MAX ` should be simplified down to true.
`MIN  > MAX ` should be simplified down to false.

`MIN  < MAX ` should be simplified down to `a != b`
`MIN  >= MAX ` should be simplified down to `a == b`