public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/41101] [4.4/4.5 Regression] ICE in compute_antic, at tree-ssa-pre.c:2419
Date: Wed, 09 Sep 2009 15:06:00 -0000	[thread overview]
Message-ID: <20090909150519.1645.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41101-5724@http.gcc.gnu.org/bugzilla/>



------- Comment #23 from rguenth at gcc dot gnu dot org  2009-09-09 15:05 -------
Subject: Bug 41101

Author: rguenth
Date: Wed Sep  9 15:04:27 2009
New Revision: 151561

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=151561
Log:
2009-09-09  Richard Guenther  <rguenther@suse.de>

        PR tree-optimization/41101
        * tree-ssa-pre.c (maximal_set): Remove.
        (compute_antic_aux): Treat the maximal set as implicitly all ones.
        Defer all blocks we didn't visit at least one successor.
        (add_to_exp_gen): Do not add to the maximal set.
        (make_values_for_phi): Likewise.
        (compute_avail): Likewise.
        (init_pre): Do not allocate the maximal set.
        (execute_pre): Do not dump it.

        * gcc.c-torture/compile/pr41101.c: New testcase.

Added:
    trunk/gcc/testsuite/gcc.c-torture/compile/pr41101.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/tree-ssa-pre.c


-- 


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


  parent reply	other threads:[~2009-09-09 15:06 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-18 10:48 [Bug other/41101] New: [4.4 regression] build doesn't terminate (endless loop?) debian-gcc at lists dot debian dot org
2009-08-18 10:49 ` [Bug other/41101] " debian-gcc at lists dot debian dot org
2009-08-18 11:18 ` [Bug tree-optimization/41101] [4.4 Regression] ICE in compute_antic, at tree-ssa-pre.c:2419 rguenth at gcc dot gnu dot org
2009-08-18 11:21 ` rguenth at gcc dot gnu dot org
2009-08-18 11:23 ` rguenth at gcc dot gnu dot org
2009-08-18 11:24 ` [Bug tree-optimization/41101] [4.4/4.5 " rguenth at gcc dot gnu dot org
2009-08-18 11:47 ` rguenth at gcc dot gnu dot org
2009-08-18 13:18 ` rguenth at gcc dot gnu dot org
2009-09-04 17:51 ` rguenth at gcc dot gnu dot org
2009-09-04 17:52 ` rguenth at gcc dot gnu dot org
2009-09-04 18:15 ` rguenth at gcc dot gnu dot org
2009-09-06 12:38 ` rguenth at gcc dot gnu dot org
2009-09-06 12:41 ` rguenth at gcc dot gnu dot org
2009-09-06 12:51 ` rguenth at gcc dot gnu dot org
2009-09-06 14:15 ` dberlin at dberlin dot org
2009-09-06 14:17 ` rguenther at suse dot de
2009-09-06 14:19 ` dberlin at dberlin dot org
2009-09-06 14:20 ` rguenther at suse dot de
2009-09-06 17:42 ` rguenth at gcc dot gnu dot org
2009-09-06 17:48 ` rguenth at gcc dot gnu dot org
2009-09-06 17:53 ` rguenth at gcc dot gnu dot org
2009-09-06 19:51 ` rguenth at gcc dot gnu dot org
2009-09-07 10:01 ` rguenth at gcc dot gnu dot org
2009-09-09 15:06 ` [Bug tree-optimization/41101] [4.4 " rguenth at gcc dot gnu dot org
2009-09-09 15:06 ` rguenth at gcc dot gnu dot org [this message]
2009-09-11 16:50 ` debian-gcc at lists dot debian dot org
2009-09-16 11:57 ` rguenth at gcc dot gnu dot org
2009-09-16 11:57 ` rguenth 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=20090909150519.1645.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).