From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E020B3858C60; Fri, 4 Nov 2022 10:29:56 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E020B3858C60 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1667557796; bh=ivfxFZjvc1ckSA3YeBu05MDaD8x2rBsoohSTZpUg+0w=; h=From:To:Subject:Date:In-Reply-To:References:From; b=T44KVw8ld8mE4KjI7lwsnfxb+U7EAVPHUMzYlVjrDRjMv4/YtRWpKEsBRwrMiMEYI gYY6TY0ejVrgA8Y006hLhRvcvrZONSCkfhyPqt1Mp/y0+E6+EvyX0UI3MRHOFTJZDY nm5cTn+Qjfzaq/HDMmKmhZGFmtgw89RWIWHUifb4= From: "redi at gcc dot 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:29:54 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 4.3.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution assigned_to bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D41041 Jonathan Wakely changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WONTFIX |--- Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu= .org Status|RESOLVED |ASSIGNED --- Comment #10 from Jonathan Wakely --- Now that we have macros exposing the execution character set, we can check = it easily: $ gcc -E -dM -x c /dev/null | grep EXEC #define __GNUC_WIDE_EXECUTION_CHARSET_NAME "UTF-32LE" #define __GNUC_EXECUTION_CHARSET_NAME "UTF-8" So the docs are misleading. I think I'll take this bug myself and try to document it without too much verbosity.=