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++/106656] [C++23] P2513 - char8_t Compatibility and Portability Fixes
Date: Mon, 26 Sep 2022 17:34:24 +0000	[thread overview]
Message-ID: <bug-106656-4-dG5koXefxY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106656-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106656

--- Comment #1 from CVS 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:567329fdd9d65a1e6254206fefff89fa151ba7f3

commit r13-2881-g567329fdd9d65a1e6254206fefff89fa151ba7f3
Author: Marek Polacek <polacek@redhat.com>
Date:   Fri Sep 23 18:06:34 2022 -0400

    c++: P2513R4, char8_t Compatibility and Portability Fix [PR106656]

    P0482R6, which added char8_t, didn't allow

      const char arr[] = u8"howdy";

    because it said "Declarations of arrays of char may currently be
initialized
    with UTF-8 string literals. Under this proposal, such initializations would
    become ill-formed."  This caused too many issues, so P2513R4 alleviates
some
    of those compatibility problems.  In particular, "Arrays of char or
unsigned
    char may now be initialized with a UTF-8 string literal."  This restriction
    has been lifted for initialization only, not implicit conversions.  Also,
    my reading is that 'signed char' was excluded from the allowable
conversions.

    This is supposed to be treated as a DR in C++20.

            PR c++/106656

    gcc/c-family/ChangeLog:

            * c-cppbuiltin.cc (c_cpp_builtins): Update value of __cpp_char8_t
            for C++20.

    gcc/cp/ChangeLog:

            * typeck2.cc (array_string_literal_compatible_p): Allow
            initializing arrays of char or unsigned char by a UTF-8 string
literal.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp23/feat-cxx2b.C: Adjust.
            * g++.dg/cpp2a/feat-cxx2a.C: Likewise.
            * g++.dg/ext/char8_t-feature-test-macro-2.C: Likewise.
            * g++.dg/ext/char8_t-init-2.C: Likewise.
            * g++.dg/cpp2a/char8_t3.C: New test.
            * g++.dg/cpp2a/char8_t4.C: New test.

  parent reply	other threads:[~2022-09-26 17:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16 17:26 [Bug c++/106656] New: " mpolacek at gcc dot gnu.org
2022-08-16 17:26 ` [Bug c++/106656] " mpolacek at gcc dot gnu.org
2022-09-26 17:34 ` cvs-commit at gcc dot gnu.org [this message]
2022-09-26 17:42 ` mpolacek at gcc dot gnu.org
2023-02-07 14:47 ` dmjpp at hotmail dot com
2023-02-07 15:06 ` 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-106656-4-dG5koXefxY@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: 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).