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:52:00 -0000 [thread overview] Message-ID: <20060330135253.28189.qmail@sourceware.org> (raw) In-Reply-To: <bug-21130-10468@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from bdavis at gcc dot gnu dot org 2006-03-30 13:52 ------- after the above patch, here is a profile of the last file (that takes so long to compile): Each sample counts as 0.01 seconds. % cumulative self self total time seconds seconds calls s/call s/call name 15.52 19.04 19.04 60138476 0.00 0.00 parse_atom 9.33 30.48 11.44 239125668 0.00 0.00 module_char 5.22 36.88 6.40 89284617 0.00 0.00 compare_integers 4.60 42.52 5.64 ht_lookup_with_hash 4.22 47.70 5.18 2224328 0.00 0.00 insert 3.56 52.07 4.37 622 0.01 0.07 load_needed 2.96 55.70 3.63 5543817 0.00 0.00 get_integer 2.63 58.93 3.23 4035787 0.00 0.00 check_interface0 2.32 61.78 2.85 312 0.01 0.03 read_cleanup 2.31 64.61 2.83 74319506 0.00 0.00 get_module_locus 2.28 67.41 2.80 21727690 0.00 0.00 set_module_locus 1.77 69.58 2.17 25323260 0.00 0.00 require_atom 1.59 71.53 1.95 4464297 0.00 0.00 clear_sym_mark 1.57 73.45 1.92 720088 0.00 0.00 count_types_test 1.56 75.36 1.91 13155211 0.00 0.00 compare_true_names 1.50 77.20 1.84 948414 0.00 0.00 traverse_ns 1.37 78.88 1.68 5424920 0.00 0.00 compare_type_rank 1.37 80.56 1.68 5424108 0.00 0.00 compare_type_rank_if --bud -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21130
next prev parent reply other threads:[~2006-03-30 13:52 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 [this message] 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=20060330135253.28189.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).