public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/19097] [3.4/4.0/4.1 regression] Quadratic behavior with many sets for the same register in gcse CPROP
Date: Mon, 19 Sep 2005 00:14:00 -0000	[thread overview]
Message-ID: <20050919001405.10588.qmail@sourceware.org> (raw)
In-Reply-To: <20041221015654.19097.phython@gcc.gnu.org>


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-09-19 00:14 -------
For -O1 on x86_64-pc-linux-gnu:

For 4.1.0:
 tree operand scan     :  18.28 (50%) usr   0.10 (18%) sys  18.33 (50%) wall     402 kB ( 0%) ggc
That is the same issue as PR 21430

For both 4.0.0 and 4.1.0:
4.0.0:
 dominance frontiers   :  12.80 (66%) usr   0.00 ( 0%) sys  12.82 (64%) wall
4.1.0:
 dominance frontiers   :  10.87 (30%) usr   0.00 ( 0%) sys  10.89 (30%) wall       0 kB ( 0%) ggc



-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
  BugsThisDependsOn|                            |21430


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19097


  parent reply	other threads:[~2005-09-19  0:14 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-21  1:57 [Bug rtl-optimization/19097] New: Lots of else ifs take forever to compile phython at gcc dot gnu dot org
2004-12-21  2:39 ` [Bug rtl-optimization/19097] " pinskia at gcc dot gnu dot org
2004-12-21  8:38 ` steven at gcc dot gnu dot org
2004-12-21  8:47 ` steven at gcc dot gnu dot org
2004-12-23  1:43 ` steven at gcc dot gnu dot org
2004-12-24  1:00 ` [Bug rtl-optimization/19097] [3.4/4.0 regression] Quadratic behavior with many sets for the same register in gcse CPROP steven at gcc dot gnu dot org
2004-12-28 18:48 ` bonzini at gcc dot gnu dot org
2005-03-05 19:53 ` [Bug rtl-optimization/19097] [3.4/4.0/4.1 " pinskia at gcc dot gnu dot org
2005-03-05 23:37 ` steven at gcc dot gnu dot org
2005-06-08  3:32 ` phython at gcc dot gnu dot org
2005-06-08  9:38 ` steven at gcc dot gnu dot org
2005-06-08 12:44 ` phython at gcc dot gnu dot org
2005-08-23  7:29 ` phython at gcc dot gnu dot org
2005-08-25  5:44 ` phython at gcc dot gnu dot org
2005-08-25  6:40 ` phython at gcc dot gnu dot org
2005-08-25  7:06 ` phython at gcc dot gnu dot org
2005-09-19  0:14 ` pinskia at gcc dot gnu dot org [this message]
2005-09-19  0:15 ` steven at gcc dot gnu dot org
2005-09-30 14:43 ` amacleod at redhat dot com
     [not found] <bug-19097-7737@http.gcc.gnu.org/bugzilla/>
2005-10-16 23:20 ` steven at gcc dot gnu dot org
2005-10-18  8:36 ` bonzini at gcc dot gnu dot org
2005-10-18 12:25 ` amacleod at redhat dot com
2005-10-29 22:38 ` steven at gcc dot gnu dot org
2005-10-31  2:02 ` mmitchel at gcc dot gnu dot org
2005-10-31 13:33 ` amacleod at redhat dot com
2005-10-31 14:41 ` amacleod at redhat dot com
2005-10-31 15:04 ` dberlin at gcc dot gnu dot org
2005-10-31 15:19 ` amacleod at gcc dot gnu dot org
2005-10-31 17:12 ` steven at gcc dot gnu dot org
2005-11-08  0:18 ` steven at gcc dot gnu dot org
2005-11-08  6:48 ` phython 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=20050919001405.10588.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: link
Be 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).