I work on a language interoperability tool called Babel. It generates F90 code
that wraps up objects written in other languages. I have an example with 38822
lines in 22 files. The last file is 4967 lines long, and it takes roughly 10
minutes to compile with a snapshot of GCC 4.0 on an essentially idle dual 3GHz
P4 Linux box. gfortran does ultimately compile the file, so I will understand if
you don't consider this a bug.
Here are the details about the version and build of gfortran:
[EMAIL PROTECTED] gfortran_issue]$
/usr/casc/babel/apps/linux_el/gcc40_pre0/bin/gcc -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../gcc-4.0-20050319/configure
--with-gmp=/usr/casc/babel/apps/linux_el/gcc40_pre0
--prefix=/usr/casc/babel/apps/linux_el/gcc40_pre0
--enable-languages=c,c++,java,f95
Thread model: posix
gcc version 4.0.0 20050319 (prerelease)
I know that tar files are not preferred, but it seems like the only reasonable
means of providing all the required files. I include a compile.sh shell script
to compile the files in the correct order. Each file is compiled with "gfortran
-c file.f90". This shows the timing output from running "sh copmile.sh".
[EMAIL PROTECTED] gfortran_issue]$ sh compile.sh
Wed Apr 20 15:27:16 PDT 2005
The following file will take roughly 10 minutes to compile
Wed Apr 20 15:27:25 PDT 2005
Wed Apr 20 15:39:18 PDT 2005
--
Summary: 38822 lines of Fortran 90 takes more than 10 minutes to
compile on a dual 3GHz P4 Linux box with lots of RAM
Product: gcc
Version: 4.0.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: epperly2 at llnl dot gov
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21130
