public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/57539] [4.9 Regression] ice in ipa_edge_duplication_hook Date: Mon, 10 Jun 2013 17:47:00 -0000 [thread overview] Message-ID: <bug-57539-4-ZbRwNR84S1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57539-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57539 --- Comment #3 from Martin Jambor <jamborm at gcc dot gnu.org> --- Created attachment 30286 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30286&action=edit Proposed fix I'm currently bootstrapping and testing this patch to fix the issue. I'll give one more thought to creating a testcase for the testsuite but constructing one is not entirely trivial.
next prev parent reply other threads:[~2013-06-10 17:47 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-06 8:55 [Bug c/57539] New: " dcb314 at hotmail dot com 2013-06-06 10:43 ` [Bug tree-optimization/57539] [4.9 Regression] " rguenth at gcc dot gnu.org 2013-06-06 10:58 ` jamborm at gcc dot gnu.org 2013-06-07 17:11 ` jamborm at gcc dot gnu.org 2013-06-10 17:47 ` jamborm at gcc dot gnu.org [this message] 2013-06-14 10:02 ` jamborm at gcc dot gnu.org 2013-06-24 12:42 ` jamborm 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-57539-4-ZbRwNR84S1@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).