public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/113760] gcc rejects valid empty-declaration in pedantic mode
Date: Mon, 05 Feb 2024 07:23:58 +0000 [thread overview]
Message-ID: <bug-113760-4-ycaL8aV1Rt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113760-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113760
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
From JDK bug report:
> It looks like it only removed
> the warnings for empty declarations at namespace scope. I couldn't find
> anything for other cases, including empty class member declarations.
Yes because the C++ defect report was only for `Spurious semicolons at
namespace scope should be allowed`. See
https://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#569 .
```
struct f
{
int t; ;
};
```
Is not allowed by the C++ standard currently and is a GCC extension, maybe it
should have a seperate flag to control that but I am not 100% sure.
next prev parent reply other threads:[~2024-02-05 7:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 7:07 [Bug c++/113760] New: " tanksherman27 at gmail dot com
2024-02-05 7:14 ` [Bug c++/113760] " pinskia at gcc dot gnu.org
2024-02-05 7:19 ` pinskia at gcc dot gnu.org
2024-02-05 7:23 ` pinskia at gcc dot gnu.org [this message]
2024-02-05 10:13 ` redi at gcc dot gnu.org
2024-02-05 14:49 ` kab at acm dot org
2024-02-05 15:10 ` [Bug c++/113760] [DR1693] " redi at gcc dot gnu.org
2024-02-07 9:29 ` jakub at gcc dot gnu.org
2024-02-12 16:38 ` mpolacek at gcc dot gnu.org
2024-02-12 16:46 ` mpolacek at gcc dot gnu.org
2024-02-12 17:07 ` mpolacek at gcc dot gnu.org
2024-02-12 21:29 ` mpolacek at gcc dot gnu.org
2024-02-12 23:36 ` harald at gigawatt dot nl
2024-02-12 23:49 ` mpolacek at gcc dot gnu.org
2024-02-13 1:17 ` harald at gigawatt dot nl
2024-02-13 1:54 ` mpolacek at gcc dot gnu.org
2024-02-13 19:27 ` mpolacek at gcc dot gnu.org
2024-02-13 23:08 ` cvs-commit at gcc dot gnu.org
2024-02-13 23:09 ` mpolacek at gcc dot gnu.org
2024-05-15 17:26 ` cvs-commit at gcc dot gnu.org
2024-05-15 17:26 ` 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-113760-4-ycaL8aV1Rt@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).