public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zeratul976 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53336] invalid types in nop conversion Date: Mon, 14 May 2012 08:52:00 -0000 [thread overview] Message-ID: <bug-53336-4-6dZXH5WQdI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53336-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53336 Nathan Ridge <zeratul976 at hotmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zeratul976 at hotmail dot | |com --- Comment #1 from Nathan Ridge <zeratul976 at hotmail dot com> 2012-05-14 08:50:53 UTC --- Reduced testcase: bool foo(); struct C { C() { if (foo()) foo(); } }; struct S { struct dummy { int i_; }; typedef int dummy::*bool_type; operator bool_type() const { return foo() ? &dummy::i_ : 0; } }; int x; struct adaptor { C c; virtual void bar() { if (S()) x = 0; } }; int main() { adaptor a; } Compile with -O2. Errors: test.cpp: In member function 'virtual void adaptor::bar()': test.cpp:32:18: error: invalid types in nop conversion virtual void bar() ^ <<< Unknown tree: offset_type >>> bool D.2314_1 = (<<< Unknown tree: offset_type >>>) D.2313_9; test.cpp:32:18: internal compiler error: verify_gimple failed
next prev parent reply other threads:[~2012-05-14 8:51 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-13 10:54 [Bug c++/53336] New: " dcb314 at hotmail dot com 2012-05-14 8:52 ` zeratul976 at hotmail dot com [this message] 2012-05-14 10:56 ` [Bug tree-optimization/53336] [4.8 Regression] " rguenth at gcc dot gnu.org 2012-05-14 10:59 ` rguenth at gcc dot gnu.org 2012-05-22 10:09 ` bonzini at gnu dot org 2012-05-31 12:29 ` 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-53336-4-6dZXH5WQdI@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).