public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/21130] New: 38822 lines of Fortran 90 takes more than 10 minutes to compile on a dual 3GHz P4 Linux box with lots of RAM
@ 2005-04-20 22:43 epperly2 at llnl dot gov
  2005-04-20 22:46 ` [Bug fortran/21130] " epperly2 at llnl dot gov
                   ` (4 more replies)
  0 siblings, 5 replies; 19+ messages in thread
From: epperly2 at llnl dot gov @ 2005-04-20 22:43 UTC (permalink / raw)
  To: gcc-bugs

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:
[epperly@tux163 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".

[epperly@tux163 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


^ permalink raw reply	[flat|nested] 19+ messages in thread
[parent not found: <bug-21130-10468@http.gcc.gnu.org/bugzilla/>]
[parent not found: <bug-21130-4@http.gcc.gnu.org/bugzilla/>]
end of thread, other threads:[~2015-10-10  9:11 UTC | newest]

Thread overview: 19+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-04-20 22:43 [Bug fortran/21130] New: 38822 lines of Fortran 90 takes more than 10 minutes to compile on a dual 3GHz P4 Linux box with lots of RAM epperly2 at llnl dot gov
2005-04-20 22:46 ` [Bug fortran/21130] " epperly2 at llnl dot gov
2005-04-21  0:03 ` pinskia at gcc dot gnu dot org
2005-04-21  0:14 ` pinskia at gcc dot gnu dot org
2005-04-24  4:05 ` jvdelisle at verizon dot net
2005-09-19  0:49 ` pinskia at gcc dot gnu dot org
     [not found] <bug-21130-10468@http.gcc.gnu.org/bugzilla/>
2006-03-02 16:10 ` rguenth at gcc dot gnu dot org
2006-03-29  1:47 ` bdavis at gcc dot gnu dot org
2006-03-29  4:32 ` howarth at nitro dot med dot uc dot edu
2006-03-30 13:52 ` bdavis at gcc dot gnu dot org
2006-03-30 13:58 ` bdavis at gcc dot gnu dot org
2006-03-30 14:04 ` bdavis at gcc dot gnu dot org
2006-03-31  0:47 ` bdavis at gcc dot gnu dot org
2006-04-17 22:53 ` bdavis at gcc dot gnu dot org
2006-05-05  5:40 ` jvdelisle at gcc dot gnu dot org
2006-05-05 18:42 ` steven at gcc dot gnu dot org
2006-05-12 16:05 ` bdavis at gcc dot gnu dot org
2006-09-20  9:23 ` paul dot thomas at jet dot uk
     [not found] <bug-21130-4@http.gcc.gnu.org/bugzilla/>
2015-10-10  9:11 ` dominiq at lps dot ens.fr

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).