public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jaffe at broad dot mit dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/23835] [4.1 Regression] case where gcc 4.1.0 -O3 compile takes two times longer earlier versions Date: Mon, 17 Oct 2005 10:01:00 -0000 [thread overview] Message-ID: <20051017100111.14333.qmail@sourceware.org> (raw) In-Reply-To: <bug-23835-8473@http.gcc.gnu.org/bugzilla/> ------- Comment #21 from jaffe at broad dot mit dot edu 2005-10-17 10:01 ------- % gcc -O3 -ftime-report -c test.ii |& grep usr | sort -t : +1 -n -r | head -10 tree SSA incremental : 3.19 (12%) usr 0.02 ( 2%) sys 3.18 (11%) wall 8995 kB ( 2%) ggc scheduling 2 : 2.03 ( 8%) usr 0.01 ( 1%) sys 2.05 ( 7%) wall 15312 kB ( 3%) ggc scheduling : 1.52 ( 6%) usr 0.00 ( 0%) sys 1.53 ( 5%) wall 7838 kB ( 2%) ggc expand : 1.32 ( 5%) usr 0.01 ( 1%) sys 1.34 ( 5%) wall 26717 kB ( 6%) ggc life analysis : 1.30 ( 5%) usr 0.00 ( 0%) sys 1.27 ( 5%) wall 3836 kB ( 1%) ggc tree alias analysis : 1.18 ( 4%) usr 0.08 ( 9%) sys 1.23 ( 4%) wall 13610 kB ( 3%) ggc parser : 1.08 ( 4%) usr 0.18 (20%) sys 1.26 ( 4%) wall 99497 kB (22%) ggc tree PTA : 1.00 ( 4%) usr 0.00 ( 0%) sys 1.01 ( 4%) wall 4565 kB ( 1%) ggc tree operand scan : 0.82 ( 3%) usr 0.14 (16%) sys 1.03 ( 4%) wall 10663 kB ( 2%) ggc integration : 0.82 ( 3%) usr 0.02 ( 2%) sys 0.84 ( 3%) wall 88155 kB (19%) ggc -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23835
next prev parent reply other threads:[~2005-10-17 10:01 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-23835-8473@http.gcc.gnu.org/bugzilla/> 2005-10-16 12:20 ` jaffe at broad dot mit dot edu 2005-10-17 9:41 ` steven at gcc dot gnu dot org 2005-10-17 10:01 ` jaffe at broad dot mit dot edu [this message] 2005-10-31 5:46 ` mmitchel at gcc dot gnu dot org 2005-10-31 10:47 ` jaffe at broad dot mit dot edu 2006-01-10 22:39 ` [Bug tree-optimization/23835] [4.1/4.2 Regression] case where gcc 4.1/4.2.0 " steven at gcc dot gnu dot org 2006-02-28 20:36 ` mmitchel at gcc dot gnu dot org 2006-05-25 2:47 ` mmitchel at gcc dot gnu dot org 2007-02-14 9:23 ` [Bug tree-optimization/23835] [4.1/4.2/4.3 Regression] case where gcc 4.1/4.2/4.3.0 " mmitchel at gcc dot gnu dot org 2007-12-18 20:09 ` steven at gcc dot gnu dot org 2007-12-19 22:02 ` ubizjak at gmail dot com 2008-07-04 20:04 ` [Bug tree-optimization/23835] [4.2/4.3/4.4 Regression] case where gcc 4.1/4.2/4.3/4.4.0 " jsm28 at gcc dot gnu dot org 2009-03-31 18:56 ` [Bug tree-optimization/23835] [4.3/4.4/4.5 Regression] -O3 compile takes two times longer jsm28 at gcc dot gnu dot org 2009-08-04 12:33 ` rguenth at gcc dot gnu dot org 2010-05-22 18:14 ` [Bug tree-optimization/23835] [4.3/4.4/4.5/4.6 " rguenth at gcc dot gnu dot org 2005-09-12 16:30 [Bug c++/23835] New: case where gcc 4.1.0 -O3 compile takes 4 times longer than gcc 3.4.3, on ia64 jaffe at broad dot mit dot edu 2005-09-15 1:28 ` [Bug tree-optimization/23835] [4.1 Regression] case where gcc 4.1.0 -O3 compile takes two times longer earlier versions cvs-commit at gcc dot gnu dot org 2005-09-15 16:40 ` pinskia at gcc dot gnu dot org 2005-09-15 16:49 ` pinskia at gcc dot gnu dot org 2005-09-15 16:50 ` pinskia at gcc dot gnu dot org 2005-09-28 9:46 ` jaffe at broad dot mit dot edu
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=20051017100111.14333.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).