Re: [PATCH] [PR107608] [range-ops] Avoid folding into INF when flag_trapping_math.

2023-01-15 Thread Aldy Hernandez via Gcc-patches
On 1/15/23 13:18, Jakub Jelinek wrote: On Sun, Jan 15, 2023 at 11:32:27AM +0100, Aldy Hernandez wrote: As discussed in the PR, for trapping math, do not fold overflowing operations into +-INF as doing so could elide a trap. There is a minor adjustment to known_isinf() where it was mistakenly

Re: [PATCH] [PR107608] [range-ops] Avoid folding into INF when flag_trapping_math.

2023-01-15 Thread Jakub Jelinek via Gcc-patches
On Sun, Jan 15, 2023 at 11:32:27AM +0100, Aldy Hernandez wrote: > As discussed in the PR, for trapping math, do not fold overflowing > operations into +-INF as doing so could elide a trap. > > There is a minor adjustment to known_isinf() where it was mistakenly > returning true for an [infinity U

[PATCH] [PR107608] [range-ops] Avoid folding into INF when flag_trapping_math.

2023-01-15 Thread Aldy Hernandez via Gcc-patches
As discussed in the PR, for trapping math, do not fold overflowing operations into +-INF as doing so could elide a trap. There is a minor adjustment to known_isinf() where it was mistakenly returning true for an [infinity U NAN], whereas it should only return true when the range is exclusively +IN

[PATCH] [PR107608] [range-ops] Avoid folding into INF when flag_trapping_math.

2023-01-15 Thread Aldy Hernandez via Gcc-patches
As discussed in the PR, for trapping math, do not fold overflowing operations into +-INF as doing so could elide a trap. There is a minor adjustment to known_isinf() where it was mistakenly returning true for an [infinity U NAN], whereas it should only return true when the range is exclusively +IN