public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dimhen at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/54980] [4.8 regression] gimple check: expected gimple_cond(error_mark), have gimple_call() in gimple_cond_set_lhs, at gimple.h:2578 Date: Thu, 18 Oct 2012 23:51:00 -0000 [thread overview] Message-ID: <bug-54980-4-YqmG5HdyN3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54980-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54980 --- Comment #2 from Dmitry G. Dyachenko <dimhen at gmail dot com> 2012-10-18 23:51:33 UTC --- more reduced $ cat 1.ii extern "C" class A { }; template < int (*t_parser) () > class B { virtual int parse () { A a; t_parser (); } }; extern "C" int f (); class C:B < f > { }; void g () { new C; } $ cat 2.ii extern "C" { void printf (const char *...); int f (); } const char *a[] = { "", 0 }; int b; int f () { while (1) switch (b) case 'h': { int i; while (a[0]) printf (a[i++]); } }
next prev parent reply other threads:[~2012-10-18 23:51 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-18 22:52 [Bug lto/54980] New: " dimhen at gmail dot com 2012-10-18 23:06 ` [Bug lto/54980] " dimhen at gmail dot com 2012-10-18 23:51 ` dimhen at gmail dot com [this message] 2012-10-19 0:09 ` dimhen at gmail dot com 2012-10-19 8:39 ` rguenth at gcc dot gnu.org 2012-10-19 10:27 ` dimhen at gmail dot com 2012-10-20 14:28 ` dimhen at gmail dot com 2012-10-23 14:48 ` hubicka at gcc dot gnu.org 2012-10-24 9:58 ` dimhen at gmail dot com 2012-10-24 10:01 ` dimhen at gmail dot com 2012-10-24 12:50 ` dimhen at gmail dot com 2012-10-25 14:52 ` hubicka at gcc dot gnu.org 2012-10-27 16:49 ` dimhen at gmail dot com
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-54980-4-YqmG5HdyN3@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).