public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "linux at carewolf dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/53460] New: Internal compiler error: in calc_dfs_tree, at dominance.c:395 Date: Wed, 23 May 2012 15:34:00 -0000 [thread overview] Message-ID: <bug-53460-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53460 Bug #: 53460 Summary: Internal compiler error: in calc_dfs_tree, at dominance.c:395 Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned@gcc.gnu.org ReportedBy: linux@carewolf.com Compiling webkit with either -fprofile-generate or -fprofile-use will cause GCC to ICE on several different files. Under any other compile flags GCC compiles the same files without any problems. There are one other open bug that ICE at the same place in GCC, but seeing that several older bugs have the same line, I assume that is no guarantee that the bug is the same, and the other bug is not related to profiling. I have included two examples, but have not reduced them.
next reply other threads:[~2012-05-23 15:32 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-23 15:34 linux at carewolf dot com [this message] 2012-05-23 15:37 ` [Bug middle-end/53460] " linux at carewolf dot com 2012-05-23 16:49 ` linux at carewolf dot com 2012-05-24 7:42 ` rguenth at gcc dot gnu.org 2012-05-24 9:29 ` rguenth at gcc dot gnu.org 2012-05-24 9:31 ` [Bug middle-end/53460] [4.7/4.8 Regression] " rguenth at gcc dot gnu.org 2012-05-24 9:47 ` rguenth at gcc dot gnu.org 2012-05-24 11:01 ` rguenth at gcc dot gnu.org 2012-05-24 11:27 ` rguenth at gcc dot gnu.org 2012-05-24 12:50 ` rguenth at gcc dot gnu.org 2012-05-24 12:50 ` rguenth at gcc dot gnu.org 2012-05-24 12:51 ` rguenth at gcc dot gnu.org 2012-05-24 13:06 ` 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=bug-53460-4@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: linkBe 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).