From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id 263C83857708 for ; Tue, 9 May 2023 19:07:16 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 263C83857708 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1683659235; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=TtRSHJn8iVcxPG8lIS2ZpgSWU+Dlott/3580EOIxtjE=; b=ZMD0yc/v+Clo02EMdGGYN1Xu3qhTkmubCo+oV367zvQUvEfuhVHwkdcflePBFOVhdZR9eK ljEWIuxf1DvQ2jOn7LdppV9/fqcujpFLhyRoUL+bui2e3C1fNdZvTVdRDKGVIILJwXgngH XGzMtHCro6DAbbYqfqBMu/6fn/EVnq4= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-184-T3iAPPpmMDClVGZXAlRdMw-1; Tue, 09 May 2023 15:07:12 -0400 X-MC-Unique: T3iAPPpmMDClVGZXAlRdMw-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 3DAB6381D1E3; Tue, 9 May 2023 19:07:12 +0000 (UTC) Received: from tucnak.zalov.cz (unknown [10.39.194.156]) by smtp.corp.redhat.com (Postfix) with ESMTPS id F1C0F40C6E67; Tue, 9 May 2023 19:07:11 +0000 (UTC) Received: from tucnak.zalov.cz (localhost [127.0.0.1]) by tucnak.zalov.cz (8.17.1/8.17.1) with ESMTPS id 349J78We1696975 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Tue, 9 May 2023 21:07:09 +0200 Received: (from jakub@localhost) by tucnak.zalov.cz (8.17.1/8.17.1/Submit) id 349J78kR1696974; Tue, 9 May 2023 21:07:08 +0200 Date: Tue, 9 May 2023 21:07:07 +0200 From: Jakub Jelinek To: Eli Zaretskii Cc: Jonathan Wakely , arsen@aarsen.me, gcc@gcc.gnu.org Subject: Re: More C type errors by default for GCC 14 Message-ID: Reply-To: Jakub Jelinek References: <877cth66qb.fsf@oldenburg.str.redhat.com> <20230509102201.6aa2a7d14fdb2f1e7abff449@killthe.net> <87r0rp5uf8.fsf@aarsen.me> <83ttwla1ep.fsf@gnu.org> <83lehx9vix.fsf@gnu.org> MIME-Version: 1.0 In-Reply-To: <83lehx9vix.fsf@gnu.org> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.2 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-3.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE autolearn=no 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 Tue, May 09, 2023 at 10:04:06PM +0300, Eli Zaretskii via Gcc wrote: > > From: Jonathan Wakely > > Date: Tue, 9 May 2023 18:15:59 +0100 > > Cc: Arsen Arsenović , gcc@gcc.gnu.org > > > > On Tue, 9 May 2023 at 17:56, Eli Zaretskii wrote: > > > > > > No one has yet explained why a warning about this is not enough, and > > > why it must be made an error. Florian's initial post doesn't explain > > > that, and none of the followups did, although questions about whether > > > a warning is not already sufficient were asked. > > > > > > That's a simple question, and unless answered with valid arguments, > > > the proposal cannot make sense to me, at least. > > > > People ignore warnings. That's why the problems have gone unfixed for > > so many years, and will continue to go unfixed if invalid code keeps > > compiling. > > People who ignore warnings will use options that disable these new > errors, exactly as they disable warnings. So we will end up not Some subset of them will surely do that. But I think most people will just fix the code when they see hard errors, rather than trying to work around them. Jakub