--- Additional Comments From gnu at the-meissners dot org 2005-07-06 19:22
---
FWIW, I tried this with the 4.0 compiler on an AMD64 system, and it doesn't fail
with gfortran.
I did bring over the 3.4.4 release, and tried it with g77, and it failed as
reported. It passed if I used -m32
--
What|Removed |Added
GCC build triplet|x86_64 GNU/Linux|
GCC host triplet|x86_64 GNU/Linux|
GCC target triplet|x86_64 GNU/Linux|x86_64-linux
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-06-12
03:23 ---
(In reply to comment #5)
> May be the following may give a hint to the g77 developers:
> if using the -fno-f2c compile option the error does not occur on AMD64
> architectures.
That means the ABI is differe
--- Additional Comments From harald dot vogt at desy dot de 2004-11-23
08:53 ---
(In reply to comment #0)
> This bug is specific for the x86_64 architecture. On 32 bit architectures it
> does not occur.
>
>
> [lx64 16:27] ~/test/cernlib/x86_64 > gcc -v -save-temps -O test1.f funct2.c
>
--- Additional Comments From Thomas dot Koenig at online dot de 2004-11-17
09:18 ---
(In reply to comment #3)
I checked this with gcc-4.0-20041107 on a ia64, and the problem didn't occur:
$ gfortran -v
Reading specs from /home/zfkts/lib/gcc/ia64-unknown-linux-gnu/4.0.0/specs
Configured
