public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/51929] [4.7 Regression] ICE: verify_cgraph_node failed with -O2 -fno-guess-branch-probability -fipa-cp-clone
Date: Thu, 09 Feb 2012 16:52:00 -0000 [thread overview]
Message-ID: <bug-51929-4-a0jwC1Lrgb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51929-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51929
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-02-09 16:51:25 UTC ---
The first testcase IMNSHO isn't a regression, because it ICEs since the
ipa-cp-eval-threshold param has been added. The other testcase is a
regression, started ICEing with the same commit:
http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=176424
next prev parent reply other threads:[~2012-02-09 16:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 11:34 [Bug middle-end/51929] New: ICE: verify_cgraph_node failed with -O2 -fno-guess-branch-probability -fipa-cp-clone --param ipa-cp-eval-threshold=0 --param max-inline-insns-single=1 zsojka at seznam dot cz
2012-02-05 15:15 ` [Bug middle-end/51929] [4.7 Regression] ICE: verify_cgraph_node failed with -O2 -fno-guess-branch-probability -fipa-cp-clone zsojka at seznam dot cz
2012-02-06 12:37 ` rguenth at gcc dot gnu.org
2012-02-07 15:40 ` rguenth at gcc dot gnu.org
2012-02-09 16:52 ` jakub at gcc dot gnu.org [this message]
2012-02-09 16:56 ` zsojka at seznam dot cz
2012-02-09 18:43 ` jakub at gcc dot gnu.org
2012-02-10 10:33 ` jakub at gcc dot gnu.org
2012-02-10 11:28 ` jakub at gcc dot gnu.org
2012-02-10 11:49 ` jakub at gcc dot gnu.org
2012-02-10 12:32 ` hubicka at gcc dot gnu.org
2012-02-16 7:34 ` jakub at gcc dot gnu.org
2012-02-16 7:47 ` jakub 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-51929-4-a0jwC1Lrgb@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).