public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/41041] Documentation: -fwide-exec-charset defaults to UCS-4/UCS-2, not UTF-32/UTF-16
Date: Fri, 04 Nov 2022 10:53:08 +0000 [thread overview]
Message-ID: <bug-41041-4-f2lek999bn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-41041-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41041
--- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> ---
SOmething like this:
--- a/gcc/doc/cppopts.texi
+++ b/gcc/doc/cppopts.texi
@@ -318,9 +318,10 @@ supported by the system's @code{iconv} library routine.
@opindex fwide-exec-charset
@cindex character set, wide execution
Set the wide execution character set, used for wide string and
-character constants. The default is UTF-32 or UTF-16, whichever
-corresponds to the width of @code{wchar_t}. As with
-@option{-fexec-charset}, @var{charset} can be any encoding supported
+character constants. The default is one of UTF-32BE, UTF-32LE, UTF-16BE,
+or UTF-16LE, whichever corresponds to the width of @code{wchar_t} and the
+big-endian or little-endian byte order being used for code generation. As
+with @option{-fexec-charset}, @var{charset} can be any encoding supported
by the system's @code{iconv} library routine; however, you will have
problems with encodings that do not fit exactly in @code{wchar_t}.
next prev parent reply other threads:[~2022-11-04 10:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-41041-4@http.gcc.gnu.org/bugzilla/>
2022-11-03 11:04 ` redi at gcc dot gnu.org
2022-11-03 11:04 ` redi at gcc dot gnu.org
2022-11-03 11:10 ` redi at gcc dot gnu.org
2022-11-03 13:38 ` samuel.thibault@ens-lyon.org
2022-11-04 10:29 ` redi at gcc dot gnu.org
2022-11-04 10:53 ` redi at gcc dot gnu.org [this message]
2022-11-05 12:37 ` cvs-commit at gcc dot gnu.org
2022-11-05 12:38 ` cvs-commit at gcc dot gnu.org
2022-11-05 12:38 ` cvs-commit at gcc dot gnu.org
2022-11-05 12:45 ` cvs-commit at gcc dot gnu.org
2022-11-05 12:45 ` redi 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-41041-4-f2lek999bn@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).