public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/46890] compile regression from 4.5 when building scummvm's player_v4a.cpp Date: Fri, 17 Dec 2010 05:55:00 -0000 [thread overview] Message-ID: <bug-46890-4-m4zihEgBka@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46890-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46890 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |NEW CC| |froydnj at codesourcery dot | |com Target Milestone|--- |4.6.0 --- Comment #5 from H.J. Lu <hjl.tools at gmail dot com> 2010-12-17 05:55:32 UTC --- A simple testcase: [hjl@gnu-35 rrs]$ cat pr46890.cc struct MdatResource { const char *mdatAlloc; } const *_resource; [hjl@gnu-35 rrs]$ ./166977/usr/bin/gcc -S pr46890.cc pr46890.cc:3:1: error: expected \u2018;\u2019 after struct definition pr46890.cc:3:10: error: ISO C++ forbids declaration of \u2018_resource\u2019 with no type [-fpermissive] [hjl@gnu-35 rrs]$ It is caused by revision 166977: http://gcc.gnu.org/ml/gcc-cvs/2010-11/msg00866.html
next prev parent reply other threads:[~2010-12-17 5:55 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-10 23:45 [Bug c++/46890] New: " matt at use dot net 2010-12-16 14:49 ` [Bug c++/46890] " rguenth at gcc dot gnu.org 2010-12-17 0:38 ` matt at use dot net 2010-12-17 0:39 ` matt at use dot net 2010-12-17 0:41 ` matt at use dot net 2010-12-17 5:55 ` hjl.tools at gmail dot com [this message] 2010-12-17 16:26 ` [Bug c++/46890] [4.6 Regression] Failed to compile " froydnj at gcc dot gnu.org 2011-01-03 20:50 ` rguenth at gcc dot gnu.org 2011-01-19 13:06 ` jakub at gcc dot gnu.org 2011-01-19 20:51 ` jakub at gcc dot gnu.org 2011-01-27 20:24 ` matt at use dot net 2011-02-03 17:16 ` froydnj at gcc dot gnu.org 2011-02-03 17:23 ` jakub at gcc dot gnu.org 2011-04-12 18:16 ` matt at use dot net
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-46890-4-m4zihEgBka@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).