https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53806
--- Comment #8 from Drea Pinski <pinskia at gcc dot gnu.org> ---
Ok, things are getting odd here.
Reading PR 53805 is getting me confused when we can remove traps and when we
can't.
Because it said this:
```
int f(double a,double b){
if(a>b) if(a<b) return 1;
return 0;
}
```
Should still cause a trap but starting in GCC 13, it is back to optimizing to 0
at -O2 with evrp doing it.
