public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/113760] [DR1693] gcc rejects valid empty-declaration in pedantic mode Date: Tue, 13 Feb 2024 23:08:50 +0000 [thread overview] Message-ID: <bug-113760-4-EOU0PTBIUI@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 #16 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>: https://gcc.gnu.org/g:6fec511f2d23cc70ab29d1ba79c2415ab51bcb60 commit r14-8967-g6fec511f2d23cc70ab29d1ba79c2415ab51bcb60 Author: Marek Polacek <polacek@redhat.com> Date: Tue Feb 13 16:21:32 2024 -0500 c++: adjust the extra ; warning [PR113760] A minimal fix to quash an extra ; warning. I have a more complete patch for GCC 15. DR 1693 PR c++/113760 gcc/cp/ChangeLog: * parser.cc (cp_parser_member_declaration): Only pedwarn about an extra semicolon in C++98. gcc/testsuite/ChangeLog: * g++.dg/semicolon-fixits.C: Run in C++98 only. * g++.dg/warn/pedantic2.C: Adjust dg-warning. * g++.old-deja/g++.jason/parse11.C: Adjust dg-error. * g++.dg/DRs/dr1693-1.C: New test. * g++.dg/DRs/dr1693-2.C: New test.
next prev parent reply other threads:[~2024-02-13 23:08 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 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 [this message] 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-EOU0PTBIUI@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).