public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: Tom Honermann <tom@honermann.net>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v4 1/2] C: Implement C2X N2653 char8_t and UTF-8 string literal changes
Date: Tue, 2 Aug 2022 22:10:32 +0000	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2208022210200.861046@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20220802183602.1575950-2-tom@honermann.net>

On Tue, 2 Aug 2022, Tom Honermann via Gcc-patches wrote:

> This patch implements the core language and compiler dependent library
> changes adopted for C2X via WG14 N2653.  The changes include:
> - Change of type for UTF-8 string literals from array of const char to
>   array of const char8_t (unsigned char).
> - A new atomic_char8_t typedef.
> - A new ATOMIC_CHAR8_T_LOCK_FREE macro defined in terms of the existing
>   __GCC_ATOMIC_CHAR8_T_LOCK_FREE predefined macro.

OK.

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2022-08-02 22:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02 18:36 [PATCH v4 0/2] Implement C2X N2653 (char8_t) and correct UTF-8 character literal type in preprocessor directives for C++ Tom Honermann
2022-08-02 18:36 ` [PATCH v4 1/2] C: Implement C2X N2653 char8_t and UTF-8 string literal changes Tom Honermann
2022-08-02 22:10   ` Joseph Myers [this message]
2022-08-02 18:36 ` [PATCH v4 2/2] preprocessor/106426: Treat u8 character literals as unsigned in char8_t modes Tom Honermann
2022-08-02 22:14   ` Joseph Myers
2022-08-08 13:45     ` Tom Honermann
2022-08-08 20:01       ` Joseph Myers

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=alpine.DEB.2.22.394.2208022210200.861046@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tom@honermann.net \
    /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).