From: Tom Honermann <tom@honermann.net>
To: Joseph Myers <joseph@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 0/3]: C N2653 char8_t implementation
Date: Fri, 11 Jun 2021 11:42:36 -0400 [thread overview]
Message-ID: <55fdc8bb-8890-c7ec-35f5-2a16da7e334a@honermann.net> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2106072057140.207568@digraph.polyomino.org.uk>
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. N2653 has not yet been
>> accepted by WG14, so no changes are made to handling of the C2X language
>> dialect.
> Why is that option needed? Normally I'd expect features to be enabled or
> disabled based on the selected language version, rather than having
> separate options to adjust the configuration for one very specific feature
> in a language version. Adding extra language dialects not corresponding
> to any standard version but to some peculiar mix of versions (such as C17
> with a changed type for u8"", or C2X with a changed type for u8'') needs a
> strong reason for those language dialects to be useful (for example, the
> -fgnu89-inline option was justified by widespread use of GNU-style extern
> inline in headers).
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).
The ability to opt-in or opt-out of the feature eases migration by
enabling source code compatibility. C and C++ standards are not
published at the same cadence. A project that targets C++20 and C17 may
therefore have a need to either opt-out of char8_t support on the C++
side (already possible via -fno-char8_t), or to opt-in to char8_t
support on the C side until such time as the targets change to C++20(+)
and C23(+); assuming WG14 approval at some point.
>
> I think the whole patch series would best wait until after the proposal
> has been considered by a WG14 meeting, in addition to not increasing the
> number of language dialects supported.
As an opt-in feature, this is useful to gain implementation and
deployment experience for WG14.
It would be appropriate to document this as an experimental feature
pending WG14 approval. If WG14 declines it or approves it with
different behavior, the feature can then be removed or changed.
The option could also be introduced as -fexperimental-char8_t if that
eases concerns, though I do not favor that approach due to misalignment
with the existing option for C++.
Tom.
next prev parent reply other threads:[~2021-06-11 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 2:31 Tom Honermann
2021-06-07 21:03 ` Joseph Myers
2021-06-11 15:42 ` Tom Honermann [this message]
2021-06-11 17:27 ` Joseph Myers
2021-06-13 15:35 ` Tom Honermann
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=55fdc8bb-8890-c7ec-35f5-2a16da7e334a@honermann.net \
--to=tom@honermann.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
/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).