This is the mail archive of the
mailing list for the GCC project.
Re: [gfortran,patch] Make MIN and MAX handle NaNs correctly (PR32048)
- From: "Andrew Pinski" <pinskia at gmail dot com>
- To: tprince at computer dot org
- Cc: "FX Coudert" <fxcoudert at gmail dot com>, "gfortran list" <fortran at gcc dot gnu dot org>, "gcc-patches list" <gcc-patches at gcc dot gnu dot org>
- Date: Sat, 28 Jul 2007 11:35:07 -0700
- Subject: Re: [gfortran,patch] Make MIN and MAX handle NaNs correctly (PR32048)
- References: <B02CF9DC-25CF-43EE-B361-2B7C60789833@gmail.com> <46AB8A43.firstname.lastname@example.org>
On 7/28/07, Tim Prince <email@example.com> wrote:
> FX Coudert wrote:
> Does this affect minval() and maxval() intrinsics? Up to now, they
> performed as well as equivalent C code with icpc, better than g++, but
> not as well as ifort. I suppose it removes the prospect of vectorizing
> code with min() and max(), unless that will be enabled with -ffast-math.
Actually the G++ code should be better on the trunk than before. If
it is not, can you file a new bug?