public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/96068] Extra semicolon outside of a function should be allowed after c++11? Date: Mon, 06 Jul 2020 16:13:46 +0000 [thread overview] Message-ID: <bug-96068-4-d0pj1qJVYH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96068-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96068 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Target Milestone|--- |11.0 Resolution|--- |FIXED --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> --- Fixed on trunk
next prev parent reply other threads:[~2020-07-06 16:13 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-05 15:33 [Bug c++/96068] New: " haoxintu at gmail dot com 2020-07-06 10:48 ` [Bug c++/96068] " redi at gcc dot gnu.org 2020-07-06 15:02 ` redi at gcc dot gnu.org 2020-07-06 16:12 ` cvs-commit at gcc dot gnu.org 2020-07-06 16:13 ` redi at gcc dot gnu.org [this message] 2021-11-08 10:31 ` pinskia at gcc dot gnu.org 2021-12-07 5:13 ` pinskia at gcc dot gnu.org 2022-05-09 16:19 ` jakub 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-96068-4-d0pj1qJVYH@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).