public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/44440] [4.6 regression] ira_initialization and buitins construction taking too much of startup time Date: Wed, 12 Jan 2011 15:01:00 -0000 [thread overview] Message-ID: <bug-44440-4-SZgtDPLkCp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-44440-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44440 Jan Hubicka <hubicka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2011.01.12 14:40:30 Summary|ira_initialization and |[4.6 regression] |buitins construction taking |ira_initialization and |too much of startup time |buitins construction taking | |too much of startup time Ever Confirmed|0 |1 --- Comment #2 from Jan Hubicka <hubicka at gcc dot gnu.org> 2011-01-12 14:40:30 UTC --- compiling empty file 100 times takes 3.8s on 4.6, while it takes 2.4s on on gcc 4.3 as well as gcc 4.5. This is 50% regression. User time increases 100%. So we probably do a lot more initialization than before. 2979 9.4936 ggc_internal_alloc_stat 1771 5.6439 ira_init 1539 4.9046 pop_scope 1258 4.0091 init_reg_sets_1 1036 3.3016 ht_lookup_with_hash 986 3.1422 ht_lookup 951 3.0307 decl_attributes 905 2.8841 ix86_hard_regno_mode_ok 852 2.7152 copy_node_stat 750 2.3901 rtx_cost 717 2.2850 bind 635 2.0236 ix86_rtx_costs 633 2.0173 ggc_internal_cleared_alloc_stat 632 2.0141 ix86_memory_move_cost 619 1.9727 c_write_global_declarations_1 566 1.8038 make_node_stat 553 1.7623 htab_find_with_hash 519 1.6540 recog 497 1.5839 iterative_hash
next parent reply other threads:[~2011-01-12 14:40 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-44440-4@http.gcc.gnu.org/bugzilla/> 2011-01-12 15:01 ` hubicka at gcc dot gnu.org [this message] 2011-02-08 15:21 ` rguenth at gcc dot gnu.org 2011-02-13 17:51 ` jsm28 at gcc dot gnu.org 2011-03-03 11:29 ` rguenth at gcc dot gnu.org 2011-03-25 19:55 ` [Bug middle-end/44440] [4.6/4.7 " jakub at gcc dot gnu.org 2011-06-27 15:27 ` jakub at gcc dot gnu.org 2011-10-26 17:17 ` jakub at gcc dot gnu.org 2012-01-20 3:49 ` pinskia at gcc dot gnu.org 2012-03-01 14:41 ` jakub at gcc dot gnu.org 2013-04-12 15:17 ` [Bug middle-end/44440] [4.7/4.8/4.9 " jakub at gcc dot gnu.org 2014-06-12 13:45 ` [Bug middle-end/44440] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org 2014-12-19 13:39 ` [Bug middle-end/44440] [4.8/4.9/5 " jakub at gcc dot gnu.org 2015-06-23 8:23 ` [Bug middle-end/44440] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org 2015-06-26 20:12 ` [Bug middle-end/44440] [4.9/5/6 " jakub at gcc dot gnu.org 2015-06-26 20:36 ` jakub at gcc dot gnu.org 2022-01-09 0:43 ` [Bug middle-end/44440] " pinskia at gcc dot gnu.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=bug-44440-4-SZgtDPLkCp@http.gcc.gnu.org/bugzilla/ \ --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).