This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/40675] Support -fnosign-zero for SIGN intrinsic for Fortran 77 compatibility
- From: "gdsjaar at sandia dot gov" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Jul 2009 21:03:12 -0000
- Subject: [Bug fortran/40675] Support -fnosign-zero for SIGN intrinsic for Fortran 77 compatibility
- References: <bug-40675-3783@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #17 from gdsjaar at sandia dot gov 2009-07-08 21:03 -------
Subject: Re: Support -fnosign-zero for SIGN
intrinsic for Fortran 77 compatibility
Thanks for the quick response. I agree that the ultimate fix is to
remove that idiom from the code; however, when dealing with decades old
fortran code, we don't always have the time or resources to do it
right. I will try to write a better test code next time that isn't
buggy...
--Greg
burnus at gcc dot gnu dot org wrote:
> ------- Comment #16 from burnus at gcc dot gnu dot org 2009-07-08 20:55 -------
> Close as FIXED (on the trunk [= 4.5]).
>
> Greg, thanks for the report. Using a 4.5/trunk build (e.g. one of the nightly
> builds) gfortran will offer the option -fno-sign-zero which allows your
> program to work.
>
> However, I still would like to suggest to change the program such that it will
> work also the default options. The problem will presumably also appear with
> other compilers - for instance if they change their default.
>
>
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40675