On 6/11/21 1:27 PM, Joseph Myers wrote:
On Fri, 11 Jun 2021, Tom Honermann via Gcc-patches wrote:
The option is needed because it impacts core language backward compatibility
(for both C and C++, the type of u8 string literals; for C++, the type of u8
character literals and the new char8_t fund
On Fri, 11 Jun 2021, Tom Honermann via Gcc-patches wrote:
> The option is needed because it impacts core language backward compatibility
> (for both C and C++, the type of u8 string literals; for C++, the type of u8
> character literals and the new char8_t fundamental type).
Lots of new features
On 6/7/21 5:03 PM, Joseph Myers wrote:
On Sun, 6 Jun 2021, Tom Honermann via Gcc-patches wrote:
These changes do not impact default gcc behavior. The existing -fchar8_t
option is extended to C compilation to enable the N2653 changes, and
-fno-char8_t is extended to explicitly disable them. N2
On Sun, 6 Jun 2021, Tom Honermann via Gcc-patches wrote:
> These changes do not impact default gcc behavior. The existing -fchar8_t
> option is extended to C compilation to enable the N2653 changes, and
> -fno-char8_t is extended to explicitly disable them. N2653 has not yet been
> accepted by W
This series of patches implements the core language features for the
WG14 N2653 [1] proposal to provide char8_t support in C. These changes
are intended to align char8_t support in C with the support provided in
C++20 via WG21 P0482R6 [2].
These changes do not impact default gcc behavior. Th
