Joseph Myers writes:
> On Fri, 28 Feb 2020, Tobias Burnus wrote:
>
>> Regarding MIN and MAX: I think the IEEE 754 decided at some point
>> decided that MAX(x, NaN) = x (IEEE 754:2008 alias ISO 60559:2011, if I
>> recall correctly). I think one has to check what exactly the test case
>> does and w
On Fri, 28 Feb 2020, Tobias Burnus wrote:
> Regarding MIN and MAX: I think the IEEE 754 decided at some point
> decided that MAX(x, NaN) = x (IEEE 754:2008 alias ISO 60559:2011, if I
> recall correctly). I think one has to check what exactly the test case
> does and what is guaranteed where. I als
On Fri, Feb 28, 2020 at 06:50:20PM +0100, Thomas Koenig wrote:
> Am 28.02.20 um 17:58 schrieb Steve Kargl:
> > Replacing MIN_EXPR/MAX_EXPR (everywhere?) would seem to
> > be a pessimization for correctly written code.
>
> Also note the following part of changes.html for 9.2:
>
> The MAX and MIN i
On Fri, Feb 28, 2020 at 04:32:05PM +0100, Jakub Jelinek wrote:
> On Fri, Feb 28, 2020 at 04:11:15PM +0100, Tobias Burnus wrote:
> > On 2/28/20 3:53 PM, Segher Boessenkool wrote:
> > > It happens with -O2 already. The frontend generates a MIN_EXPR (or
> > > MAX_EXPR) for this, which is undefined for
Am 28.02.20 um 17:58 schrieb Steve Kargl:
Replacing MIN_EXPR/MAX_EXPR (everywhere?) would seem to
be a pessimization for correctly written code.
Also note the following part of changes.html for 9.2:
The MAX and MIN intrinsics are no longer guaranteed to return any
particular value in case one
On Fri, Feb 28, 2020 at 04:11:15PM +0100, Tobias Burnus wrote:
> On 2/28/20 3:53 PM, Segher Boessenkool wrote:
> > It happens with -O2 already. The frontend generates a MIN_EXPR (or
> > MAX_EXPR) for this, which is undefined for NaNs already. I think the
> > testcase is just invalid?
>
> Ups, that
On Fri, Feb 28, 2020 at 04:04:10PM +0100, Jakub Jelinek wrote:
> On Fri, Feb 28, 2020 at 08:53:11AM -0600, Segher Boessenkool wrote:
> > On Thu, Feb 27, 2020 at 09:25:27PM -0800, Steve Kargl wrote:
> > > On Fri, Feb 28, 2020 at 01:02:28PM +0800, Jiufu Guo wrote:
> > > >
> > > > With -ffast-math -O
On Fri, Feb 28, 2020 at 04:11:15PM +0100, Tobias Burnus wrote:
> On 2/28/20 3:53 PM, Segher Boessenkool wrote:
> > It happens with -O2 already. The frontend generates a MIN_EXPR (or
> > MAX_EXPR) for this, which is undefined for NaNs already. I think the
> > testcase is just invalid?
>
> Ups, that
On 2/28/20 3:53 PM, Segher Boessenkool wrote:
It happens with -O2 already. The frontend generates a MIN_EXPR (or
MAX_EXPR) for this, which is undefined for NaNs already. I think the
testcase is just invalid?
Ups, that shouldn't happen. It does seem to work here
(x86-64-gnu-linux), however, runn
On Fri, Feb 28, 2020 at 08:53:11AM -0600, Segher Boessenkool wrote:
> On Thu, Feb 27, 2020 at 09:25:27PM -0800, Steve Kargl wrote:
> > On Fri, Feb 28, 2020 at 01:02:28PM +0800, Jiufu Guo wrote:
> > >
> > > With -ffast-math -O3, this case `STOP 3` on a few platforms, e.g.
> > > ppc64le/x86.
> >
>
Hi Tobias,
On Fri, Feb 28, 2020 at 10:58:36AM +0100, Tobias Burnus wrote:
> (Do you really need to post to gcc@, fortran@ and gcc-patches@?
> Shouldn't be one of the list sufficient – like fortran@?)
Many people do not read that list. I asked Jiu Fu to post to both
fortran@ and one of gcc@ and g
On Thu, Feb 27, 2020 at 09:25:27PM -0800, Steve Kargl wrote:
> On Fri, Feb 28, 2020 at 01:02:28PM +0800, Jiufu Guo wrote:
> >
> > With -ffast-math -O3, this case `STOP 3` on a few platforms, e.g.
> > ppc64le/x86.
>
> IMHO, using -ffast-math with Fortran code is never correct.
> With this option,
Hi,
(Do you really need to post to gcc@, fortran@ and gcc-patches@?
Shouldn't be one of the list sufficient – like fortran@?)
On 2/28/20 6:02 AM, Jiufu Guo wrote:
When I check a PR93709, I find the testcase maxlocval_4.f90 […]
With -ffast-math -O3, this case `STOP 3` on a few platforms, e.g.
On Fri, Feb 28, 2020 at 01:02:28PM +0800, Jiufu Guo wrote:
>
> With -ffast-math -O3, this case `STOP 3` on a few platforms, e.g. ppc64le/x86.
>
IMHO, using -ffast-math with Fortran code is never correct.
With this option, you got exactly what you wanted.
--
Steve
Hi,
When I check a PR93709, I find the testcase maxlocval_4.f90 and
minlocval_4.f90 are checking `maxval/minval` on `-inf` and `nan`.
https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;a=blob_plain;f=gcc/testsuite/gfortran.dg/maxlocval_4.f90;hb=HEAD
There are code like:
```
l5 = .true.
l5(1,1) = .false.
Hi,
When I check a PR93709, I find the testcase maxlocval_4.f90 and
minlocval_4.f90 are checking `maxval/minval` on `-inf` and `nan`.
https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;a=blob_plain;f=gcc/testsuite/gfortran.dg/maxlocval_4.f90;hb=HEAD
There are code like:
```
l5 = .true.
l5(1,1) = .false.
16 matches
Mail list logo