public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/46183] [4.6 Regression] ICE: in calc_dfs_tree, at dominance.c:396 with -O -fno-dse -fgcse -ftree-pre
Date: Tue, 02 Nov 2010 14:37:00 -0000 [thread overview]
Message-ID: <20101102143700.xmexoJqrJIvwgZh3ENyK0YZFcch9eZjxLTRYXZ_fjqw@z> (raw)
In-Reply-To: <bug-46183-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46183
Steven Bosscher <steven at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |steven at gcc dot gnu.org
--- Comment #4 from Steven Bosscher <steven at gcc dot gnu.org> 2010-11-02 14:37:21 UTC ---
There is nothing weird about the comment before the quoted code. It just
mentions that the simple solver for global CPROP does not work if there are
unreachable blocks in the CFG (and that the DF solver is insensitive to this).
But oh well, I'll have a look...
next prev parent reply other threads:[~2010-11-02 14:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 13:35 [Bug tree-optimization/46183] New: " zsojka at seznam dot cz
2010-10-26 13:52 ` [Bug tree-optimization/46183] " rguenth at gcc dot gnu.org
2010-10-26 15:03 ` hjl.tools at gmail dot com
2010-10-27 1:58 ` jakub at gcc dot gnu.org
2010-10-29 12:52 ` rguenth at gcc dot gnu.org
2010-11-02 13:58 ` rguenth at gcc dot gnu.org
2010-11-02 14:37 ` steven at gcc dot gnu.org [this message]
2010-11-02 14:48 ` steven at gcc dot gnu.org
2010-11-02 15:03 ` steven at gcc dot gnu.org
2010-11-02 16:04 ` ebotcazou at gcc dot gnu.org
2010-11-04 14:02 ` rguenth at gcc dot gnu.org
2010-11-04 15:19 ` rguenth at gcc dot gnu.org
2010-11-04 15:21 ` rguenth at gcc dot gnu.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=20101102143700.xmexoJqrJIvwgZh3ENyK0YZFcch9eZjxLTRYXZ_fjqw@z \
--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).