From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by sourceware.org (Postfix) with ESMTP id AD3E83858412 for ; Tue, 10 Oct 2023 10:48:11 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org AD3E83858412 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=arm.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=arm.com Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 2248F1FB; Tue, 10 Oct 2023 03:48:52 -0700 (PDT) Received: from [10.2.78.54] (e120077-lin.cambridge.arm.com [10.2.78.54]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id EF4C83F7A6; Tue, 10 Oct 2023 03:48:10 -0700 (PDT) Message-ID: <085179e2-3ed7-7bf3-b682-326656db378c@arm.com> Date: Tue, 10 Oct 2023 11:48:09 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.15.0 Subject: Re: Documenting common C/C++ options Content-Language: en-GB To: Florian Weimer , gcc@gcc.gnu.org References: <877cnubygs.fsf@oldenburg.str.redhat.com> From: "Richard Earnshaw (lists)" In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3493.9 required=5.0 tests=BAYES_00,KAM_DMARC_NONE,KAM_DMARC_STATUS,KAM_LAZY_DOMAIN_SECURITY,NICE_REPLY_A,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 10/10/2023 11:46, Richard Earnshaw (lists) via Gcc wrote: > On 10/10/2023 10:47, Florian Weimer via Gcc wrote: >> Currently, -fsigned-char and -funsigned-char are only documented as C >> language options, although they work for C++ as well (and Objective-C >> and Objective-C++, I assume, but I have not tested this). There does >> not seem to be a place for this kind of options in the manual. >> >> The options -fshort-enums and -fshort-wchar are documented under >> code-generation options, but this seems to be a bit of a stretch because >> (at least for -fshort-wchar), these too seem to be more about front-end >> behavior. >> >> What would be a good way to address this? >> >> Thanks, >> Florian >> > > > All of these are ABI; so where ever it goes, it should be documented that changing them will potentially cause issues with any pre-compiled object files having different settings. > > R. And you can add -f[un]signed-bitfield to that list as well. R.