public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bdavis at gcc dot gnu dot org" <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: Thu, 30 Mar 2006 13:58:00 -0000 [thread overview] Message-ID: <20060330135800.30950.qmail@sourceware.org> (raw) In-Reply-To: <bug-21130-10468@http.gcc.gnu.org/bugzilla/> ------- Comment #10 from bdavis at gcc dot gnu dot org 2006-03-30 13:58 ------- with the same patch, the aermod.f90 : Each sample counts as 0.01 seconds. % cumulative self self total time seconds seconds calls s/call s/call name 7.69 8.80 8.80 29723933 0.00 0.00 parse_atom 5.26 14.82 6.02 125084260 0.00 0.00 module_char 3.51 18.83 4.01 record_reg_classes 2.83 22.07 3.24 find_reloads 2.19 24.58 2.51 walk_tree 1.85 26.70 2.12 2331175 0.00 0.00 gt_ggc_mx_lang_tree_node 1.77 28.73 2.03 ht_lookup_with_hash 1.72 30.70 1.97 ggc_set_mark 1.48 32.39 1.69 ggc_alloc_stat 1.37 33.96 1.57 10696036 0.00 0.00 set_module_locus 1.27 35.41 1.45 13353395 0.00 0.00 require_atom 1.14 36.71 1.30 722236 0.00 0.00 gfc_match_strings 1.12 37.99 1.28 817282 0.00 0.00 insert 1.12 39.27 1.28 constrain_operands 1.08 40.50 1.23 31922526 0.00 0.00 get_module_locus 1.03 41.68 1.18 3220 0.00 0.00 traverse_ns 0.94 42.76 1.08 706 0.00 0.02 load_needed --bud -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21130
next prev parent reply other threads:[~2006-03-30 13:58 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 2006-03-30 13:52 ` bdavis at gcc dot gnu dot org 2006-03-30 13:58 ` bdavis at gcc dot gnu dot org [this message] 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=20060330135800.30950.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: linkBe 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).