--- Comment #7 from al dot danial at ngc dot com 2009-07-13 21:13 ---
One more data point: the build machine runs CentOS 4.3 and on it gfortran
works fine (!). The ICE happens on a CentOS 4.4 box (using the identical GCC
4.4.0/GMP 4.2.2/MPFR 2.4.1 bits from a shared NFS mount).
I'll m
--- Comment #6 from al dot danial at ngc dot com 2009-07-13 18:51 ---
(In reply to comment #5)
> My guess would be you have configured libgmp or libmpfr for a different CPU
> than you really have. Try
> gdb --args /apps/gcc/4.4.0/libexec/gcc/i686-pc-linux-gnu/4.4.0/f951 hello.f
> run
>
--- Comment #5 from jakub at gcc dot gnu dot org 2009-07-13 18:42 ---
My guess would be you have configured libgmp or libmpfr for a different CPU
than you really have. Try
gdb --args /apps/gcc/4.4.0/libexec/gcc/i686-pc-linux-gnu/4.4.0/f951 hello.f
run
and see on which insn it crashed (d
--- Comment #4 from al dot danial at ngc dot com 2009-07-13 18:33 ---
(In reply to comment #2)
> Try compiling without these:
>
>
> -lgfortranbegin -lgfortran
>
> Should not need to do this. Lets see what it does.
I don't specify either of these options (or any others for that matt
--- Comment #3 from al dot danial at ngc dot com 2009-07-13 18:30 ---
(In reply to comment #1)
> Fortran reports are never anything but "normal".
>
> However, would you really expect that a compiler would be released that can't
> handle code like the one quoted? I find it hard to belie
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2009-07-13 18:12
---
Try compiling without these:
-lgfortranbegin -lgfortran
Should not need to do this. Lets see what it does.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40734
--- Comment #1 from dfranke at gcc dot gnu dot org 2009-07-13 18:00 ---
Fortran reports are never anything but "normal".
However, would you really expect that a compiler would be released that can't
handle code like the one quoted? I find it hard to believe, especially on a
platform as
