public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "haoxintu at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/95724] New: bogue error : "expected '{' before ')' token"
Date: Wed, 17 Jun 2020 16:45:08 +0000	[thread overview]
Message-ID: <bug-95724-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95724

            Bug ID: 95724
           Summary: bogue error : "expected '{' before ')' token"
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: haoxintu at gmail dot com
  Target Milestone: ---

This code test.cc, GCC-trunk get a bogus error message and then get confused
with following code parsing.

$cat test.cc
template <(union : decltype(a = 0)>)


$g++-trunk -w -c test.cc
test.cc:1:11: error: expected identifier before ‘(’ token
    1 | template <(union : decltype(a = 0)>)
      |           ^
test.cc:1:29: error: ‘a’ was not declared in this scope
    1 | template <(union : decltype(a = 0)>)
      |                             ^
test.cc:1:29: error: ‘a’ was not declared in this scope
test.cc:1:34: error: expected ‘{’ before ‘)’ token
    1 | template <(union : decltype(a = 0)>)
      |                                  ^
test.cc:1:36: error: expected unqualified-id before ‘)’ token
    1 | template <(union : decltype(a = 0)>)
      |                                    ^

$g++-10 -w -c test.cc
test.cc:1:11: error: expected identifier before ‘(’ token
    1 | template <(union : decltype(a = 0)>)
      |           ^
test.cc:1:29: error: ‘a’ was not declared in this scope
    1 | template <(union : decltype(a = 0)>)
      |                             ^
test.cc:1:29: error: ‘a’ was not declared in this scope
test.cc:1:35: error: expected ‘{’ before ‘>’ token
    1 | template <(union : decltype(a = 0)>)
      |                                   ^
test.cc:1:35: error: expected ‘,’ or ‘...’ before ‘>’ token
test.cc:1:36: error: expected ‘>’ at end of input
    1 | template <(union : decltype(a = 0)>)
      |                                    ^
test.cc:1:36: error: expected unqualified-id at end of input

I guess GCC-trunk emits the bogus error message "expected ‘{’ before ‘)’
token", and the following error messages are inconsistent with GCC-10. So,
GCC-trunk might have something wrong with while parsing this code.

             reply	other threads:[~2020-06-17 16:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-17 16:45 haoxintu at gmail dot com [this message]
2020-06-17 17:43 ` [Bug c++/95724] " marxin at gcc dot gnu.org
2020-06-17 17:54 ` haoxintu at gmail dot com
2020-06-17 18:58 ` marxin at gcc dot gnu.org
2020-06-18  8:33 ` rguenth at gcc dot gnu.org
2020-06-18  8:37 ` marxin at gcc dot gnu.org
2020-06-18 11:37 ` redi at gcc dot gnu.org
2020-06-18 12:25 ` rguenth at gcc dot gnu.org
2022-01-07  2:35 ` [Bug c++/95724] error message could be improved in the cascading error case pinskia 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-95724-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: link
Be 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).