public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/100977] New: [C++23] Implement C++ Identifier Syntax using Unicode Standard Annex 31 Date: Tue, 08 Jun 2021 18:15:40 +0000 [thread overview] Message-ID: <bug-100977-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100977 Bug ID: 100977 Summary: [C++23] Implement C++ Identifier Syntax using Unicode Standard Annex 31 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: jason at gcc dot gnu.org Blocks: 98940 Target Milestone: --- https://wg21.link/p1949r7 This seems like largely a matter of adding another category to libcpp/ucnid.tab. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98940 [Bug 98940] Implement C++23 language features
next reply other threads:[~2021-06-08 18:15 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-08 18:15 jason at gcc dot gnu.org [this message] 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 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@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).