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/61211] [4.9/4.10 Regression] ICE: verify_cgraph_node failed: edge points to wrong declaration with -O3 -fno-inline Date: Fri, 20 Jun 2014 09:58:00 -0000 [thread overview] Message-ID: <bug-61211-4-57sSUwl0oq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61211-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61211 --- Comment #4 from Martin Jambor <jamborm at gcc dot gnu.org> --- Author: jamborm Date: Fri Jun 20 09:57:53 2014 New Revision: 211845 URL: https://gcc.gnu.org/viewcvs?rev=211845&root=gcc&view=rev Log: 2014-06-20 Martin Jambor <mjambor@suse.cz> PR ipa/61211 * cgraph.c (clone_of_p): Allow skipped_branch to deal with expanded clones. Modified: branches/gcc-4_9-branch/gcc/ChangeLog branches/gcc-4_9-branch/gcc/cgraph.c
next prev parent reply other threads:[~2014-06-20 9:58 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-61211-4@http.gcc.gnu.org/bugzilla/> 2014-05-30 13:28 ` jamborm at gcc dot gnu.org 2014-05-30 22:48 ` jamborm at gcc dot gnu.org 2014-06-20 9:55 ` jamborm at gcc dot gnu.org 2014-06-20 9:58 ` jamborm at gcc dot gnu.org [this message] 2014-06-20 10:01 ` 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-61211-4-57sSUwl0oq@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).