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++/100977] [C++23] Implement C++ Identifier Syntax using Unicode Standard Annex 31 Date: Tue, 30 Nov 2021 08:51:40 +0000 [thread overview] Message-ID: <bug-100977-4-KZ2v4wbH68@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100977-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100977 --- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:7abcc9ca20d4e17deabb308b5f483aaccc3dc02c commit r12-5597-g7abcc9ca20d4e17deabb308b5f483aaccc3dc02c Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Nov 30 09:50:52 2021 +0100 libcpp: Enable P1949R7 for C++11 and up as it was a DR [PR100977] Jonathan mentioned on IRC that: "Accept P1949R7 (C++ Identifier Syntax using Unicode Standard Annex 31) as a Defect Report and apply the changes therein to the C++ working paper." while I've actually implemented it only for -std={gnu,c}++{23,2b}. As the C++98 rules were significantly different, I'm not trying to change anything for C++98. 2021-11-30 Jakub Jelinek <jakub@redhat.com> PR c++/100977 * init.c (lang_defaults): Enable cxx23_identifiers for -std={gnu,c}++{11,14,17,20} too. * c-c++-common/cpp/ucnid-2011-1-utf8.c: Expect errors in C++. * c-c++-common/cpp/ucnid-2011-1.c: Likewise. * g++.dg/cpp/ucnid-4-utf8.C: Add missing space to dg-options. * g++.dg/cpp23/normalize3.C: Enable for c++11 rather than just c++23. * g++.dg/cpp23/normalize4.C: Likewise. * g++.dg/cpp23/normalize5.C: Likewise. * g++.dg/cpp23/normalize7.C: Expect errors rather than just warnings for c++11 and up rather than just c++23. * g++.dg/cpp23/ucnid-2-utf8.C: Expect errors even for c++11 .. c++20.
next prev parent reply other threads:[~2021-11-30 8:51 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-08 18:15 [Bug c++/100977] New: " jason at gcc dot gnu.org 2021-06-08 18:19 ` [Bug c++/100977] " mpolacek at gcc dot gnu.org 2021-08-04 13:39 ` jakub at gcc dot gnu.org 2021-08-04 14:08 ` jakub at gcc dot gnu.org 2021-08-04 16:14 ` jakub at gcc dot gnu.org 2021-08-04 18:34 ` joseph at codesourcery dot com 2021-08-04 18:40 ` jakub at gcc dot gnu.org 2021-08-04 19:06 ` ubizjak at gmail dot com 2021-08-04 19:20 ` jakub at gcc dot gnu.org 2021-08-04 19:25 ` ubizjak at gmail dot com 2021-08-05 10:17 ` jakub at gcc dot gnu.org 2021-08-05 15:34 ` cvs-commit at gcc dot gnu.org 2021-08-05 15:35 ` cvs-commit at gcc dot gnu.org 2021-09-01 20:37 ` cvs-commit at gcc dot gnu.org 2021-09-01 20:38 ` jakub at gcc dot gnu.org 2021-11-30 8:51 ` cvs-commit at gcc dot gnu.org [this message] 2021-12-01 9:22 ` cvs-commit 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-100977-4-KZ2v4wbH68@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).