public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med dot uc dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
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
Date: Wed, 29 Mar 2006 04:32:00 -0000 [thread overview]
Message-ID: <20060329043237.19655.qmail@sourceware.org> (raw)
In-Reply-To: <bug-21130-10468@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from howarth at nitro dot med dot uc dot edu 2006-03-29 04:32 -------
I can confirm this patch resolves the test case on MacOS X with gcc 4.1
branch...
Before patch...
Tue Mar 28 23:06:11 EST 2006
The following file will take roughly 10 minutes to compile
Tue Mar 28 23:06:23 EST 2006
Tue Mar 28 23:25:00 EST 2006
After patch...
Tue Mar 28 23:26:00 EST 2006
The following file will take roughly 10 minutes to compile
Tue Mar 28 23:26:12 EST 2006
Tue Mar 28 23:27:03 EST 2006
This is on a dual 2.0GHz G5 with 2 Gb of RAM. However I don't see any
significant impact
on the compile time for the aermod polyhedron benchmark.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21130
next prev parent reply other threads:[~2006-03-29 4:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
2005-04-20 22:43 [Bug fortran/21130] New: " 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060329043237.19655.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).