From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23242 invoked by alias); 20 Sep 2006 09:23:03 -0000 Received: (qmail 23214 invoked by uid 48); 20 Sep 2006 09:22:56 -0000 Date: Wed, 20 Sep 2006 09:23:00 -0000 Message-ID: <20060920092256.23213.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/21130] 38822 lines of Fortran 90 takes more than 10 minutes to compile on a dual 3GHz P4 Linux box with lots of RAM In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "paul dot thomas at jet dot uk" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-09/txt/msg01895.txt.bz2 List-Id: ------- Comment #16 from paul dot thomas at jet dot uk 2006-09-20 09:22 ------- (In reply to comment #15) > looks like there is agreement that the problem is fixed. I am afraid to say that I do not agree entirely; the above takes 6 seconds to compile with ifort on my Athlon 1700 "a vapeur". The patch is pretty good but Andrew is right to say in PR25708 that we should not be loading the modules repeatedly. I put a counter in read_module to check how many times each module was read, in the above, and came to the conclusion that gfortran would achieve the same compile time as ifort, if we were to read a module once into a separate symtree and use and abuse it from there. For my sins, I have proposed to do this as a gfortran-4.3 project. Paul -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21130