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 ipa/61160] [4.9/4.10 Regression] wrong code with -O3 (or ICE: verify_cgraph_node failed: edge points to wrong declaration) Date: Fri, 30 May 2014 23:20:00 -0000 [thread overview] Message-ID: <bug-61160-4-uTwAPkr1av@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61160-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61160 --- Comment #4 from Martin Jambor <jamborm at gcc dot gnu.org> --- These are in fact two different issues. I proposed the following to patches on the mailing list to address them: https://gcc.gnu.org/ml/gcc-patches/2014-05/msg02658.html and https://gcc.gnu.org/ml/gcc-patches/2014-05/msg02660.html
next prev parent reply other threads:[~2014-05-30 23:20 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-05-12 19:48 [Bug ipa/61160] New: " zsojka at seznam dot cz 2014-05-12 19:50 ` [Bug ipa/61160] " zsojka at seznam dot cz 2014-05-28 15:37 ` jamborm at gcc dot gnu.org 2014-05-30 23:20 ` jamborm at gcc dot gnu.org [this message] 2014-06-03 10:10 ` jamborm at gcc dot gnu.org 2014-06-03 10:13 ` jamborm at gcc dot gnu.org 2014-06-03 10:16 ` jamborm at gcc dot gnu.org 2014-06-26 13:05 ` rguenth at gcc dot gnu.org 2014-06-27 11:32 ` jamborm at gcc dot gnu.org 2014-06-27 13:29 ` jamborm at gcc dot gnu.org 2014-06-29 20:41 ` jamborm at gcc dot gnu.org 2014-06-30 11:35 ` christophe.lyon at st dot com 2014-07-03 8:31 ` jakub at gcc dot gnu.org 2014-07-16 16:40 ` jamborm at gcc dot gnu.org 2014-07-22 16:21 ` jamborm at gcc dot gnu.org 2014-07-24 13:04 ` jamborm at gcc dot gnu.org 2014-07-24 13:21 ` jamborm at gcc dot gnu.org 2014-09-30 0:08 ` sandra at codesourcery dot com 2015-07-08 11:25 ` 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-61160-4-uTwAPkr1av@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).