public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/51421] New: [c++0x] ICE with invalid use of auto Date: Mon, 05 Dec 2011 07:51:00 -0000 [thread overview] Message-ID: <bug-51421-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51421 Bug #: 51421 Summary: [c++0x] ICE with invalid use of auto Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: reichelt@gcc.gnu.org The following invalid code snippet triggers an ICE since GCC 4.4.0: ===================== int foo(int); void bar() { auto i = foo(i); } ===================== bug.cc: In function 'void bar()': bug.cc:5:17: internal compiler error: tree check: expected record_type or union_type or qual_union_type, have template_type_parm in lookup_conversions, at cp/search.c:2499 Please submit a full bug report, [etc.] A slightly different example triggers an ICE in a different position: ===================== struct A {}; A foo(A); void bar() { auto a = foo(a); } ===================== bug.cc: In function 'void bar()': bug.cc:7:17: internal compiler error: tree check: expected record_type or union_type or qual_union_type, have template_type_parm in lookup_base, at cp/search.c:212 Please submit a full bug report, [etc.]
next reply other threads:[~2011-12-05 7:51 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-05 7:51 reichelt at gcc dot gnu.org [this message] 2012-01-21 9:41 ` [Bug c++/51421] " pinskia at gcc dot gnu.org 2012-08-24 21:16 ` paolo.carlini at oracle dot com 2012-08-25 9:53 ` paolo at gcc dot gnu.org 2012-08-25 9:54 ` paolo.carlini at oracle 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-51421-4@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).