From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cc-smtpout3.netcologne.de (cc-smtpout3.netcologne.de [IPv6:2001:4dd0:100:1062:25:2:0:3]) by sourceware.org (Postfix) with ESMTPS id 15039385840E for ; Fri, 12 May 2023 09:11:44 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 15039385840E Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=netcologne.de Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=netcologne.de Received: from cc-smtpin1.netcologne.de (cc-smtpin1.netcologne.de [89.1.8.201]) by cc-smtpout3.netcologne.de (Postfix) with ESMTP id C3F86121F0; Fri, 12 May 2023 11:11:41 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=netcologne.de; s=nc1116a; t=1683882701; bh=koX7ppwMhtLD9uEDJl9Tu5RKix/Hg5RLBIxHeYDp93M=; h=Message-ID:Date:Subject:To:Cc:References:From:In-Reply-To:From; b=GnvU5clMjMSLwnRm5M8QVdesXOzYA3LKvGUmfiZoxcAROr5KKdKOP9HrxhBrfWYSR HMNjBNyZm3Nu/3K6q4ri7UZ7aCcfKytg0/2q4bn9HtbNNcDf+EmdkgKDK1uEptweS0 vOZvcDMEBA7nsBTpnD/JWFr28SxbPBpdDAkEHF1FNl2yDuSfmElhZLhimQccq5sG4U Jor1PRMFdXAQFDajvNu+vb+ChRwAwHLrpbLvptndz3dzTXUMAlboZdHomFpS8BbVbL Z/of53lGQ8YJ0GIwCOofnZY+yPTc5UNi41bkLoYFniEYJuKLbxTR/zVTvD5HR2o3Y3 dp5eWkJeYnVbA== Received: from [IPV6:2001:4dd6:3fec:0:7285:c2ff:fe6c:992d] (2001-4dd6-3fec-0-7285-c2ff-fe6c-992d.ipv6dyn.netcologne.de [IPv6:2001:4dd6:3fec:0:7285:c2ff:fe6c:992d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by cc-smtpin1.netcologne.de (Postfix) with ESMTPSA id 42D181208B; Fri, 12 May 2023 11:11:40 +0200 (CEST) Message-ID: <55cba636-f477-bb02-060b-c94fa4173983@netcologne.de> Date: Fri, 12 May 2023 11:11:39 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: More C type errors by default for GCC 14 Content-Language: en-US To: Eli Zaretskii Cc: gcc@gcc.gnu.org References: <877cth66qb.fsf@oldenburg.str.redhat.com> <20230509102201.6aa2a7d14fdb2f1e7abff449@killthe.net> <87r0rp5uf8.fsf@aarsen.me> <83ttwla1ep.fsf@gnu.org> <83lehx9vix.fsf@gnu.org> <83fs859unu.fsf@gnu.org> <87y1lx1avj.fsf@oldenburg.str.redhat.com> <83ednoapb6.fsf@gnu.org> <875y8zegnc.fsf@yahoo.com> <865y8zmi08.fsf@aarsen.me> <87bkirclqv.fsf@yahoo.com> <86a5ybjlbd.fsf@aarsen.me> <83ilcz5f5e.fsf@gnu.org> <865y8y8tjr.fsf@aarsen.me> <834joi3s07.fsf@gnu.org> From: Thomas Koenig In-Reply-To: <834joi3s07.fsf@gnu.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-NetCologne-Spam: L X-Rspamd-Queue-Id: 42D181208B X-Rspamd-Action: no action X-Spamd-Bar: - X-Spam-Status: No, score=-4.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_NUMSUBJECT,NICE_REPLY_A,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE 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 12.05.23 09:53, Eli Zaretskii via Gcc wrote: > I described in an earlier message how this breakage looks in real > life, and why it causes a lot of frustration. The main problem is > discovering that things broke because GCC defaults, and then > discovering how to pacify GCC with the least effort. Gcc is quite helpful these days: $ gcc -c example.c example.c:1:1: warning: data definition has no type or storage class 1 | a(); | ^ example.c:1:1: warning: type defaults to 'int' in declaration of 'a' [-Wimplicit-int] $ gcc -Werror -c example.c example.c:1:1: error: data definition has no type or storage class [-Werror] 1 | a(); | ^ example.c:1:1: error: type defaults to 'int' in declaration of 'a' [-Werror=implicit-int] (sorry, cannot show the nice coloring). It tells you right in the error message which option caused the or warning in question. This is not hard. Is your opinion that reading error messages (and making the mental leap of adding the negative, of course) is too much to expect? Best regards Thomas