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/55797] [4.8 Regression] ICE: verify_cgraph_node failed: edge has no corresponding call_stmt Date: Wed, 23 Jan 2013 13:49:00 -0000 [thread overview] Message-ID: <bug-55797-4-xgXahGzcKE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55797-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55797 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-01-23 13:49:17 UTC --- For 4.9, wouldn't it be better to get all functions through the very early passes (up to and including build_ssa (or one or three passes after it, but before pass_inline_parameters)), then in another loop run the rest of early passes (i.e. inline_parameters/einline, ..., eipa_sra, ..., pass_inline_parameters) and then the normal IPA queue? The amount of issues we have with functions not in SSA form yet, whether it is in early inliner, or eipa_sra, etc. is big.
next prev parent reply other threads:[~2013-01-23 13:49 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-23 11:04 [Bug middle-end/55797] New: " zsojka at seznam dot cz 2012-12-26 22:20 ` [Bug middle-end/55797] " pinskia at gcc dot gnu.org 2012-12-30 10:54 ` mpolacek at gcc dot gnu.org 2012-12-30 12:16 ` mpolacek at gcc dot gnu.org 2013-01-07 15:44 ` rguenth at gcc dot gnu.org 2013-01-08 13:51 ` rguenth at gcc dot gnu.org 2013-01-08 14:25 ` rguenth at gcc dot gnu.org 2013-01-23 13:29 ` hubicka at gcc dot gnu.org 2013-01-23 13:38 ` hubicka at gcc dot gnu.org 2013-01-23 13:49 ` jakub at gcc dot gnu.org [this message] 2013-01-23 13:57 ` hubicka at gcc dot gnu.org 2013-01-23 14:00 ` hubicka at gcc dot gnu.org 2013-01-23 14:20 ` hubicka at gcc dot gnu.org 2013-02-08 11:30 ` 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-55797-4-xgXahGzcKE@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).