public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Richard Guenther <rguenth@tat.physik.uni-tuebingen.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/10196: [3.3/3.4 regression] Compile time regression with inlining Date: Tue, 08 Apr 2003 14:46:00 -0000 [thread overview] Message-ID: <20030408144601.13751.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/10196; it has been noted by GNATS. From: Richard Guenther <rguenth@tat.physik.uni-tuebingen.de> To: gcc-gnats@gcc.gnu.org Cc: gcc-bugs@gcc.gnu.org, <nobody@gcc.gnu.org> Subject: Re: optimization/10196: [3.3/3.4 regression] Compile time regression with inlining Date: Tue, 8 Apr 2003 16:42:16 +0200 (CEST) Got some profiles from g++ (GCC) 3.3 20030408 (prerelease) for the testcases (with and without exception handling enabled) at http://www.tat.physik.uni-tuebingen.de/~rguenth/DynamicLayout.cmpl.ii.ex.prof.gz for the testcase at http://www.tat.physik.uni-tuebingen.de/~rguenth/DynamicLayout2.cmpl.ii.gz compiled with -O2 and http://www.tat.physik.uni-tuebingen.de/~rguenth/DynamicLayout.cmpl.ii.noex.prof.gz for the testcase at http://www.tat.physik.uni-tuebingen.de/~rguenth/DynamicLayout.cmpl.ii.noex.gz compiled with -O2 -fno-exceptions The top of the (flat) profiles is for the -fno-exceptions case: % cumulative self self total time seconds seconds calls ms/call ms/call name 5.82 0.80 0.80 766758 0.00 0.00 walk_tree 2.62 1.16 0.36 2894249 0.00 0.00 htab_find_slot_with_hash 2.25 1.47 0.31 1 310.00 13483.20 yyparse 1.75 1.71 0.24 3031555 0.00 0.00 ggc_alloc 1.45 1.91 0.20 4068886 0.00 0.00 statement_code_p 1.45 2.11 0.20 460662 0.00 0.00 splay_tree_splay_helper 1.31 2.29 0.18 1667085 0.00 0.00 timevar_push 1.31 2.47 0.18 486047 0.00 0.00 for_each_rtx 1.24 2.64 0.17 2731899 0.00 0.00 htab_find_slot 1.24 2.81 0.17 102119 0.00 0.00 cse_insn 1.24 2.98 0.17 68502 0.00 0.00 gt_ggc_mx_lang_tree_node 1.09 3.13 0.15 3334173 0.00 0.00 get_time and for the -fexceptions case: % cumulative self self total time seconds seconds calls ms/call ms/call name 6.92 11.24 11.24 1531056 0.01 0.02 walk_tree 6.61 21.97 10.73 1048564 0.01 0.01 flow_delete_block_noexpunge 4.72 29.63 7.66 3413593 0.00 0.00 emit_insn 2.97 34.46 4.83 1767371 0.00 0.00 gt_ggc_mx_lang_tree_node 2.66 38.78 4.32 17457 0.25 0.25 clear_table 2.63 43.05 4.27 20409582 0.00 0.00 copy_node 2.56 47.21 4.16 1582 2.63 2.71 init_alias_analysis 2.39 51.10 3.89 42221301 0.00 0.00 ggc_alloc 1.98 54.32 3.22 86395200 0.00 0.00 statement_code_p 1.95 57.48 3.16 52652842 0.00 0.00 ggc_set_mark 1.83 60.46 2.98 3539665 0.00 0.00 gt_ggc_mx_rtx_def 1.70 63.22 2.76 23360833 0.00 0.00 copy_tree_r But I dont really know where to look for (remember, -fno-default-inline sort of "fixes" the problem, too). Richard.
next reply other threads:[~2003-04-08 14:46 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-08 14:46 Richard Guenther [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-23 15:46 mmitchel 2003-04-08 11:06 Steven Bosscher 2003-04-08 11:06 Richard Guenther 2003-04-08 9:56 Steven Bosscher 2003-04-07 15:06 Steven Bosscher 2003-03-24 18:26 mmitchel 2003-03-24 13:46 Richard Guenther 2003-03-24 8:36 mmitchel
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=20030408144601.13751.qmail@sources.redhat.com \ --to=rguenth@tat.physik.uni-tuebingen.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).