public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "theubik at mail dot ru" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/64248] New: Error: declarator-id missing; using reserved word ‘__FUNCTION__’ Date: Wed, 10 Dec 2014 06:53:00 -0000 [thread overview] Message-ID: <bug-64248-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64248 Bug ID: 64248 Summary: Error: declarator-id missing; using reserved word ‘__FUNCTION__’ Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: theubik at mail dot ru Created attachment 34236 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34236&action=edit gcc -v output class A { public: A(const char* str) {}; }; class B { public: B(A a) {}; }; int main() { B b(A(__FUNCTION__)); return 0; } > gcc main.cpp main.cpp: In function ‘int main()’: main.cpp:15:22: error: declarator-id missing; using reserved word ‘__FUNCTION__’ B b(A(__FUNCTION__)); ^ gcc was built from snapshot http://gcc.skazkaforyou.com/snapshots/5-20141207/ os Linux ubik 3.2.0-70-generic #105-Ubuntu SMP Wed Sep 24 19:49:16 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux >From gcc-bugs-return-469996-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 10 07:01:56 2014 Return-Path: <gcc-bugs-return-469996-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 23156 invoked by alias); 10 Dec 2014 07:01:56 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 23123 invoked by uid 48); 10 Dec 2014 07:01:51 -0000 From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/60694] Gcc-4.2.4 hangs during compilation of the attached test Date: Wed, 10 Dec 2014 07:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 4.2.4 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mpolacek at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution Message-ID: <bug-60694-4-MWyZ5UQNd1@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-60694-4@http.gcc.gnu.org/bugzilla/> References: <bug-60694-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-12/txt/msg01003.txt.bz2 Content-length: 518 https://gcc.gnu.org/bugzilla/show_bug.cgi?id`694 Marek Polacek <mpolacek at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |mpolacek at gcc dot gnu.org Resolution|--- |FIXED --- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Already fixed thus.
next reply other threads:[~2014-12-10 6:53 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-10 6:53 theubik at mail dot ru [this message] 2014-12-10 7:06 ` [Bug c++/64248] [5 Regression] " trippels at gcc dot gnu.org 2014-12-10 7:46 ` theubik at mail dot ru 2014-12-10 7:48 ` trippels at gcc dot gnu.org 2014-12-10 12:25 ` rguenth at gcc dot gnu.org 2014-12-10 22:38 ` jason at gcc dot gnu.org 2014-12-12 3:49 ` jason at gcc dot gnu.org 2014-12-12 3:57 ` jason 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-64248-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).