public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/62091] [5 Regression] ice in before_dom_children
Date: Wed, 13 Aug 2014 18:45:00 -0000 [thread overview]
Message-ID: <bug-62091-4-5LHEAMBT4B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62091-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62091
--- Comment #3 from Jan Hubicka <hubicka at ucw dot cz> ---
> Honza - these should always be gcc_checking_assert ()s - there is no need to
> ICE (and in fact it shouldn't even be a gcc_checking_assert in any tree but
> yours used for testing).
Yep, I plan to remove the old intraprocedural code very soon - I am basically
looking for testcases like these. I went through firefox/testsuite/Qt builds
myself, but wanted to know if there are more side cases.
Honza
next prev parent reply other threads:[~2014-08-13 18:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 15:47 [Bug c++/62091] New: " dcb314 at hotmail dot com
2014-08-13 8:32 ` [Bug tree-optimization/62091] [4.10 Regression] " rguenth at gcc dot gnu.org
2014-08-13 18:45 ` hubicka at ucw dot cz [this message]
2014-08-14 23:36 ` [Bug tree-optimization/62091] [5 " hubicka at gcc dot gnu.org
2014-08-19 14:48 ` dcb314 at hotmail dot com
2014-08-19 16:27 ` dcb314 at hotmail dot com
2014-08-19 18:26 ` jason at gcc dot gnu.org
2014-08-19 18:30 ` jason at gcc dot gnu.org
2014-08-20 1:55 ` jason at gcc dot gnu.org
2014-08-20 2:04 ` jason at gcc dot gnu.org
2014-08-20 16:02 ` hubicka at ucw dot cz
2014-08-20 16:19 ` trippels at gcc dot gnu.org
2014-08-21 13:49 ` hubicka at gcc dot gnu.org
2014-09-25 20:13 ` hubicka 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=bug-62091-4-5LHEAMBT4B@http.gcc.gnu.org/bugzilla/ \
--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).