--- Additional Comments From tobi at gcc dot gnu dot org 2005-01-06 14:27
---
Looks like I didn't close this bug, when I said I would.
--
What|Removed |Added
Sta
--- Additional Comments From tobi at gcc dot gnu dot org 2004-10-21 15:25 ---
We actually do have a warning for this: -Wconversion, which is currently not
enabled with -Wall. I'm closing this bug, but if you are in favor of adding this
warning to -Wall, Jerry, feel free to propose a patch
--- Additional Comments From tobi at gcc dot gnu dot org 2004-10-12 21:26 ---
(In reply to comment #4)
> I tried this same program with g95 before I submitted a bug and got what
> I thought was the correct results without needing the additional _8 .
> Do the standards specify that defaul
--- Additional Comments From anlauf at hep dot tu-darmstadt dot de 2004-10-12
06:55 ---
(In reply to comment #4)
> Subject: Re: Math error in simple divide operation
>
> I suppose then that a warning would be good when mixing precisions in
> assignments.
With Fortran 77, the great fre
--- Additional Comments From jvdelisle at verizon dot net 2004-10-12 04:57 ---
Subject: Re: Math error in simple divide operation
On Mon, 2004-10-11 at 09:00, tobi at gcc dot gnu dot org wrote:
> --- Additional Comments From tobi at gcc dot gnu dot org 2004-10-11 16:00
> ---
>
--- Additional Comments From tobi at gcc dot gnu dot org 2004-10-11 16:00 ---
Actually, looking at this again, gfortran's behavior is correct.
If you had written
big = 2.0_8 / 3.0_8
you would have gotten the result you were expecting.
I think, adding a warning would be the best route f
--- Additional Comments From tobi at gcc dot gnu dot org 2004-10-11 15:54 ---
gfortran uses its own constant folder, which uses the mpfr library. Apparently
the precision is too low for double precision. Output from -fdump-parse-tree
includes:
ASSIGN big 6.6686534882e-1_8
So it'
--- Additional Comments From pinskia at gcc dot gnu dot org 2004-10-11 05:28
---
Confirmed, this is a front-end problem, we are not getting enough precission for some
reason (really I
don't know the rules of fortran). I will note the equivalent C code works just fine
on the same bui