public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/115516] New: constexpr use before C23 could give a better error message
@ 2024-06-17  6:04 pinskia at gcc dot gnu.org
  2024-06-18  5:58 ` [Bug c/115516] " rguenth at gcc dot gnu.org
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: pinskia at gcc dot gnu.org @ 2024-06-17  6:04 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 115516
           Summary: constexpr use before C23 could give a better error
                    message
           Product: gcc
           Version: 15.0
            Status: UNCONFIRMED
          Keywords: diagnostic
          Severity: enhancement
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: pinskia at gcc dot gnu.org
  Target Milestone: ---

Take:
```
constexpr int j = 1;
```

Currently we give:
```
<source>:1:10: error: expected ';' before 'int'
    1 | constexpr int j = 1;
      |          ^~~~
      |          ;
```

This could give a better error message just like the C++ front-end does for
C++98:
```
<source>:1:1: error: 'constexpr' does not name a type
    1 | constexpr int j = 1;
      | ^~~~~~~~~
<source>:1:1: note: C++11 'constexpr' only available with '-std=c++11' or
'-std=gnu++11'
```

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug c/115516] constexpr use before C23 could give a better error message
  2024-06-17  6:04 [Bug c/115516] New: constexpr use before C23 could give a better error message pinskia at gcc dot gnu.org
@ 2024-06-18  5:58 ` rguenth at gcc dot gnu.org
  2024-06-18  6:13 ` jakub at gcc dot gnu.org
  2024-06-18  6:18 ` jakub at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: rguenth at gcc dot gnu.org @ 2024-06-18  5:58 UTC (permalink / raw)
  To: gcc-bugs

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2024-06-18
             Status|UNCONFIRMED                 |NEW

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug c/115516] constexpr use before C23 could give a better error message
  2024-06-17  6:04 [Bug c/115516] New: constexpr use before C23 could give a better error message pinskia at gcc dot gnu.org
  2024-06-18  5:58 ` [Bug c/115516] " rguenth at gcc dot gnu.org
@ 2024-06-18  6:13 ` jakub at gcc dot gnu.org
  2024-06-18  6:18 ` jakub at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: jakub at gcc dot gnu.org @ 2024-06-18  6:13 UTC (permalink / raw)
  To: gcc-bugs

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
It will be hard, because constexpr before C++11 is not a keyword.
And it can't be, int constexpr = 1; is completely valid C++98.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug c/115516] constexpr use before C23 could give a better error message
  2024-06-17  6:04 [Bug c/115516] New: constexpr use before C23 could give a better error message pinskia at gcc dot gnu.org
  2024-06-18  5:58 ` [Bug c/115516] " rguenth at gcc dot gnu.org
  2024-06-18  6:13 ` jakub at gcc dot gnu.org
@ 2024-06-18  6:18 ` jakub at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: jakub at gcc dot gnu.org @ 2024-06-18  6:18 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Sorry, this was about C, not C++.  And apparently C++ manages to warn about
that in
cp_parser_diagnose_invalid_type_name through
if (cxx_dialect < cxx11 && id == ridpointers[(int)RID_CONSTEXPR])
check.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2024-06-18  6:18 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-06-17  6:04 [Bug c/115516] New: constexpr use before C23 could give a better error message pinskia at gcc dot gnu.org
2024-06-18  5:58 ` [Bug c/115516] " rguenth at gcc dot gnu.org
2024-06-18  6:13 ` jakub at gcc dot gnu.org
2024-06-18  6:18 ` jakub 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).