This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/37930] gfortran error and ICE at automatic type conversion with transfer intrinsic
- From: "sgk at troutmask dot apl dot washington dot edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 31 Oct 2008 22:14:57 -0000
- Subject: [Bug fortran/37930] gfortran error and ICE at automatic type conversion with transfer intrinsic
- References: <bug-37930-8911@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #26 from sgk at troutmask dot apl dot washington dot edu 2008-10-31 22:14 -------
Subject: Re: gfortran error and ICE at automatic type conversion with transfer
intrinsic
On Fri, Oct 31, 2008 at 09:43:13PM -0000, burnus at gcc dot gnu dot org wrote:
>
> > I'll also note that the diagnostic information tells you how to
> > disable the range checking.
>
> That is actually not true: For ARITH_NAN and ARITH_UNDERFLOW there is no
> -fno-range-check mentioned - only for ARITH_OVERFLOW is.
I don't use -fno-range-check unless I'm debugging some PR,
so I forgot the details. ARITH_UNDERFLOW doesn't require
any special handling (ie., they are set to zero). We could
extend -fno-range-check to allow the conversion of a REAL
NaN to a DOUBLE PRECISION NaN. I'm not too excited by that
idea.
> Question: Is this bug now fixed or remains something else to do? (Besides
> mentioning -fno-range-check in the error message and implementing F2003's IEEE
> functions.)
Personally, I think the bug is fixed, and this PR can be closed.
I thought FX had opened a PR for the IEEE module, but a quick
scan did not find it. I guess it doesn't make much sense opening
a PR for every unimplemented F2003 feature.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37930