Building the GCC compiler for the language "Fortran" fails in bootstrapping
mode. Strangely, I am able to build the Fortran compiler in native
non-bootstrapping mode.

If I do start the build in bootstrapping mode, it finally fails with the
following error (I will attach the complete log):

***************************************************
configure:14187: /scratch/rjeurnin/gcc/gcc-4.4.2-B10/build/./gcc/gfortran
-B/scratch/rjeurnin/gcc/gcc-4.4.2-B10/build/./gcc/
-B/scratch/rjeurnin/gcc/gcc-4.4.2-B10/install/sparc-sun-solaris2.10/bin/
-B/scratch/rjeurnin/gcc/gcc-4.4.2-B10/install/sparc-sun-solaris2.10/lib/
-isystem
/scratch/rjeurnin/gcc/gcc-4.4.2-B10/install/sparc-sun-solaris2.10/include
-isystem
/scratch/rjeurnin/gcc/gcc-4.4.2-B10/install/sparc-sun-solaris2.10/sys-include
-c -g -O2  conftest.f >&5
f951: internal compiler error: Arithmetic Exception
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
configure:14193: $? = 1
configure: failed program was:
| 
|       program foo
|       real, parameter :: bar = sin (12.34 / 2.5)
|       end program foo
***************************************************

Running the testsuite on the bootstrapped build will (obviously) give very poor
results for the fortran part. This confirms that the fortran compiler is messed
up seriously.

Hope you can help me as I'm completely stuck on this one.
thanks,

Roger


-- 
           Summary: Bootstrapping Fortran with GCC 4.4.2 fails on Solaris
                    5.10: "f951: internal compiler error: Arithmetic
                    Exception"
           Product: gcc
           Version: 4.4.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: Roger dot Jeurninck at home dot nl
 GCC build triplet: sparc-sun-solaris2.10
  GCC host triplet: sparc-sun-solaris2.10
GCC target triplet: sparc-sun-solaris2.10


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42723

Reply via email to