public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/95724] New: bogue error : "expected '{' before ')' token"
@ 2020-06-17 16:45 haoxintu at gmail dot com
2020-06-17 17:43 ` [Bug c++/95724] " marxin at gcc dot gnu.org
` (7 more replies)
0 siblings, 8 replies; 9+ messages in thread
From: haoxintu at gmail dot com @ 2020-06-17 16:45 UTC (permalink / raw)
To: gcc-bugs
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.
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug c++/95724] bogue error : "expected '{' before ')' token"
2020-06-17 16:45 [Bug c++/95724] New: bogue error : "expected '{' before ')' token" haoxintu at gmail dot com
@ 2020-06-17 17:43 ` marxin at gcc dot gnu.org
2020-06-17 17:54 ` haoxintu at gmail dot com
` (6 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: marxin at gcc dot gnu.org @ 2020-06-17 17:43 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95724
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marxin at gcc dot gnu.org
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
For the next time, can you please add 'ice-on-invalid-code' keyword?
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug c++/95724] bogue error : "expected '{' before ')' token"
2020-06-17 16:45 [Bug c++/95724] New: bogue error : "expected '{' before ')' token" haoxintu at gmail dot com
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
` (5 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: haoxintu at gmail dot com @ 2020-06-17 17:54 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95724
--- Comment #2 from Haoxin Tu <haoxintu at gmail dot com> ---
(In reply to Martin Liška from comment #1)
> For the next time, can you please add 'ice-on-invalid-code' keyword?
I got it. So sorry for my mistake!
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug c++/95724] bogue error : "expected '{' before ')' token"
2020-06-17 16:45 [Bug c++/95724] New: bogue error : "expected '{' before ')' token" haoxintu at gmail dot com
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
` (4 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: marxin at gcc dot gnu.org @ 2020-06-17 18:58 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95724
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Haoxin Tu from comment #2)
> (In reply to Martin Liška from comment #1)
> > For the next time, can you please add 'ice-on-invalid-code' keyword?
>
> I got it. So sorry for my mistake!
It's not a mistake, I just wanted to inform you that it's very unlikely that
we'll fix it. We have a lot of these issues..
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug c++/95724] bogue error : "expected '{' before ')' token"
2020-06-17 16:45 [Bug c++/95724] New: bogue error : "expected '{' before ')' token" haoxintu at gmail dot com
` (2 preceding siblings ...)
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
` (3 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: rguenth at gcc dot gnu.org @ 2020-06-18 8:33 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95724
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Note the testcase does not ICE so ice-on-invalid is wrong. It's really
a diagnostic only. If we want sth extra to distinguish error diagnostics
from warning diagnostics then we should add one (can't come up with a good name
right now)
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug c++/95724] bogue error : "expected '{' before ')' token"
2020-06-17 16:45 [Bug c++/95724] New: bogue error : "expected '{' before ')' token" haoxintu at gmail dot com
` (3 preceding siblings ...)
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
` (2 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: marxin at gcc dot gnu.org @ 2020-06-18 8:37 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95724
--- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #4)
> Note the testcase does not ICE so ice-on-invalid is wrong. It's really
> a diagnostic only. If we want sth extra to distinguish error diagnostics
> from warning diagnostics then we should add one (can't come up with a good
> name right now)
Yes, I was too eager..
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug c++/95724] bogue error : "expected '{' before ')' token"
2020-06-17 16:45 [Bug c++/95724] New: bogue error : "expected '{' before ')' token" haoxintu at gmail dot com
` (4 preceding siblings ...)
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
7 siblings, 0 replies; 9+ messages in thread
From: redi at gcc dot gnu.org @ 2020-06-18 11:37 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95724
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #4)
> Note the testcase does not ICE so ice-on-invalid is wrong. It's really
> a diagnostic only. If we want sth extra to distinguish error diagnostics
> from warning diagnostics then we should add one (can't come up with a good
> name right now)
It's like a weaker form of error-recovery but for cases that don't ICE.
cascading-errors maybe.
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug c++/95724] bogue error : "expected '{' before ')' token"
2020-06-17 16:45 [Bug c++/95724] New: bogue error : "expected '{' before ')' token" haoxintu at gmail dot com
` (5 preceding siblings ...)
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
7 siblings, 0 replies; 9+ messages in thread
From: rguenth at gcc dot gnu.org @ 2020-06-18 12:25 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95724
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #6)
> (In reply to Richard Biener from comment #4)
> > Note the testcase does not ICE so ice-on-invalid is wrong. It's really
> > a diagnostic only. If we want sth extra to distinguish error diagnostics
> > from warning diagnostics then we should add one (can't come up with a good
> > name right now)
>
> It's like a weaker form of error-recovery but for cases that don't ICE.
error-recovery is fine then I guess since it doens't imply ICEing. We
use the combo of ice-on-invalid-code, error-recovery for that. But indeed
the description says 'use only for ice-on-invalid-code' ...
> cascading-errors maybe.
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug c++/95724] error message could be improved in the cascading error case
2020-06-17 16:45 [Bug c++/95724] New: bogue error : "expected '{' before ')' token" haoxintu at gmail dot com
` (6 preceding siblings ...)
2020-06-18 12:25 ` rguenth at gcc dot gnu.org
@ 2022-01-07 2:35 ` pinskia at gcc dot gnu.org
7 siblings, 0 replies; 9+ messages in thread
From: pinskia at gcc dot gnu.org @ 2022-01-07 2:35 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95724
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Summary|bogue error : "expected '{' |error message could be
|before ')' token" |improved in the cascading
| |error case
Ever confirmed|0 |1
Last reconfirmed| |2022-01-07
Severity|normal |enhancement
--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I don't like the error messages from any of the other compilers I tried either:
clang:
<source>:2:29: error: use of undeclared identifier 'a'
template <(union : decltype(a = 0)>)
^
<source>:2:36: error: expected '{' after base class list
template <(union : decltype(a = 0)>)
^
<source>:2:12: error: '(unnamed union at <source>:2:12)' cannot be defined in a
parameter type
template <(union : decltype(a = 0)>)
^
<source>:2:37: error: expected template parameter
template <(union : decltype(a = 0)>)
^
<source>:2:37: error: expected ',' or '>' in template-parameter-list
<source>:2:37: error: expected unqualified-id
MSVC:
<source>(2): error C2059: syntax error: '('
<source>(2): error C2947: expecting '>' to terminate template-parameter-list,
found '>'
<source>(2): error C2059: syntax error: ')'
<source>(3): fatal error C1004: unexpected end-of-file found
ICC:
<source>(2): error: expected a type specifier
template <(union : decltype(a = 0)>)
^
<source>(2): error: expected a "," or ">"
<source>(2): error: expected a declaration
<source>(2): error: expected a ";"
compilation aborted for <source> (code 2)
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2022-01-07 2:35 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-06-17 16:45 [Bug c++/95724] New: bogue error : "expected '{' before ')' token" haoxintu at gmail dot com
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
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).