public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rs2740 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/64679] New: Spurious redefinition error when parsing not-quite-most-vexing-parse declarations Date: Tue, 20 Jan 2015 01:30:00 -0000 [thread overview] Message-ID: <bug-64679-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64679 Bug ID: 64679 Summary: Spurious redefinition error when parsing not-quite-most-vexing-parse declarations Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: rs2740 at gmail dot com Repro: class Bar{ public: Bar(int, int, int); }; int main () { int x = 1; Bar bar(int(x), int(x), int{x}); } gcc HEAD 5.0.0 20150119 (experimental) with g++ prog.cc -Wall -Wextra -std=gnu++1y reports: prog.cc: In function 'int main()': prog.cc:8:24: error: redefinition of 'int x' Bar bar(int(x), int(x), int{x}); ^ prog.cc:8:16: note: 'int x' previously declared here Bar bar(int(x), int(x), int{x}); With the last int{x} (note the braces) this cannot be a function declaration, but g++ appears to emit the redefinition errors too early, before the full declaration is parsed. Clang compiles this successfully.
next reply other threads:[~2015-01-20 1:30 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-20 1:30 rs2740 at gmail dot com [this message] 2022-04-29 19:06 ` [Bug c++/64679] " mpolacek at gcc dot gnu.org 2022-05-04 20:06 ` cvs-commit at gcc dot gnu.org 2022-05-05 21:34 ` cvs-commit at gcc dot gnu.org 2022-05-05 21:37 ` mpolacek 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-64679-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).