public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/20742] New: [4.0/4.1 Regression] Hang in tree_ssa_iv_optimize_loop
Date: Mon, 04 Apr 2005 11:38:00 -0000	[thread overview]
Message-ID: <20050404113801.20742.jakub@gcc.gnu.org> (raw)

The following testcase (simplified from lmbench) causes major compile time
regression in tree_ssa_iv_optimize_loop.
Without -DHANG (and with -O2), HEAD gcc needs 0m34.176s, while with GCC 3.4.x
0m0.035s.  On 4.0 branch it even takes substantially longer.
lmbench has 100 such lines, which would take longer than anybody could wait.

-- 
           Summary: [4.0/4.1 Regression] Hang in tree_ssa_iv_optimize_loop
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jakub at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org,rakdver at gcc dot gnu
                    dot org,sebastian dot pop at cri dot ensmp dot fr


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


             reply	other threads:[~2005-04-04 11:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-04 11:38 jakub at gcc dot gnu dot org [this message]
2005-04-04 11:38 ` [Bug tree-optimization/20742] " jakub at gcc dot gnu dot org
2005-04-04 11:41 ` jakub at gcc dot gnu dot org
2005-04-04 13:02 ` pinskia at gcc dot gnu dot org
2005-04-04 14:03 ` rakdver at gcc dot gnu dot org
2005-04-04 14:51 ` sebastian dot pop at cri dot ensmp dot fr
2005-04-05  1:36 ` pinskia at gcc dot gnu dot org
2005-04-07  6:21 ` pinskia at gcc dot gnu dot org
2005-04-21  5:04 ` mmitchel at gcc dot gnu dot org
2005-04-21 20:57 ` [Bug tree-optimization/20742] [4.0 " cvs-commit at gcc dot gnu dot org
2005-05-03 23:05 ` cvs-commit at gcc dot gnu dot org
2005-06-06 12:13 ` cvs-commit at gcc dot gnu dot org
2005-06-06 12:59 ` pinskia at gcc dot gnu dot org
2005-06-07 19:54 ` cvs-commit 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=20050404113801.20742.jakub@gcc.gnu.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).