Alright, I know everyon'es pretty busy and I am blocking myself here,
so I hereby approve my own patch, since I am the maintainer ;-).
After all, I'd like to have 5-6 days to field any possible fallout
before I disappear off to a tropical island to drink mojitos and beer.
Ok, not really-- just cha
PING
Andrew, anyone, would you mind giving this a once over? I realize
reviewing ranger's range-op code is not on anyone's list of
priorities, but I could use a sanity check.
The patch is sufficiently self-contained to easily catch anything
caused by it, and I'd like to commit earlier in the wee
I forgot to mention. There's a regression in g++.dg/opt/pr94589-2.C,
where an early optimization by evrp causes phiopt to no longer
optimize a spaceship operator because it no longer sees the exact
sequence of conditionals. I have included the analysis in the patch.
Hopefully a phiopt expert can
Without further ado, here is the implementation for floating point
range operators, plus the switch to enable all ranger clients to
handle floats.
These are bare bone implementations good enough for relation operators
to work, while keeping the NAN bits up to date in the frange. There
is also min
