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 rtl-optimization/48721] [4.6/4.7 Regression] ICE: verify_flow_info failed: missing barrier after block 6 with -foptimize-sibling-calls -fsched2-use-superblocks Date: Wed, 30 Nov 2011 13:22:00 -0000 [thread overview] Message-ID: <bug-48721-4-cXQI5p11BW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48721-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48721 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vmakarov at gcc dot gnu.org --- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-11-30 12:55:15 UTC --- Vlad, could you please look at that?
next prev parent reply other threads:[~2011-11-30 12:55 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-22 0:05 [Bug rtl-optimization/48721] New: " zsojka at seznam dot cz 2011-06-12 12:40 ` [Bug rtl-optimization/48721] " rguenth at gcc dot gnu.org 2011-06-12 13:31 ` rguenth at gcc dot gnu.org 2011-06-27 15:51 ` jakub at gcc dot gnu.org 2011-08-01 8:27 ` [Bug rtl-optimization/48721] [4.6 " ubizjak at gmail dot com 2011-08-25 0:53 ` [Bug rtl-optimization/48721] [4.6/4.7 " pinskia at gcc dot gnu.org 2011-08-25 1:40 ` pinskia at gcc dot gnu.org 2011-08-25 1:47 ` pinskia at gcc dot gnu.org 2011-10-26 17:13 ` jakub at gcc dot gnu.org 2011-11-30 12:55 ` jakub at gcc dot gnu.org 2011-11-30 13:17 ` jakub at gcc dot gnu.org 2011-11-30 13:22 ` jakub at gcc dot gnu.org [this message] 2011-11-30 15:23 ` jakub at gcc dot gnu.org 2011-11-30 19:01 ` jakub at gcc dot gnu.org 2011-11-30 19:21 ` jakub at gcc dot gnu.org 2011-11-30 20:53 ` [Bug rtl-optimization/48721] [4.6 " jakub at gcc dot gnu.org 2011-12-08 13:37 ` jakub at gcc dot gnu.org 2011-12-08 13:43 ` 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-48721-4-cXQI5p11BW@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).