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 A976F385771B for ; Tue, 16 May 2023 08:56:00 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org A976F385771B 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=1684227360; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=BTk0Cmni9HjkrdP0+6XsyKyxssmzeSV1P1Mb584UHTc=; b=AjlEGaesVb+BAV4DyuCQwUcsDaq4StMKquP4AUu8ANTFa3JpItV8YGJROYzS4/HOw0F3jb s4X8UDOkd29DAfVVUW6Wm3Rlvoa4OSWwNqxH3R2SaycuGzACnXV0Oe9L6qSGUd8YFQos4m BqGHsLvgyVrrIHF3x+Q+M7M0tjv1ZeM= 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-440-JVMqiUG6N4GqXg4RfobOWw-1; Tue, 16 May 2023 04:55:58 -0400 X-MC-Unique: JVMqiUG6N4GqXg4RfobOWw-1 Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 5A7102A59542; Tue, 16 May 2023 08:55:58 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.2.16.25]) by smtp.corp.redhat.com (Postfix) with ESMTPS id C2516492B01; Tue, 16 May 2023 08:55:56 +0000 (UTC) From: Florian Weimer To: Michael Matz Cc: Alexander Monakov , Gabriel Ravier , Joseph Myers , Eli Zaretskii , Jakub Jelinek , jwakely.gcc@gmail.com, gcc@gcc.gnu.org, arsen@aarsen.me Subject: Re: More C type errors by default for GCC 14 References: <87y1lx1avj.fsf@oldenburg.str.redhat.com> <83ednoapb6.fsf@gnu.org> <831qjoa0g0.fsf@gnu.org> <83o7ms8is7.fsf@gnu.org> <2ffbf210-1b58-737b-888c-4f84c5cc5e0f@gmail.com> <837ctg8e98.fsf@gnu.org> <83wn1g6w67.fsf@gnu.org> <83mt2c6tch.fsf@gnu.org> <871qjlh9t3.fsf@mid.deneb.enyo.de> <87jzxdfne0.fsf@mid.deneb.enyo.de> <3d157d9c-0504-b8b4-46f6-54ea90374765@gmail.com> <4989d9fb-366a-4103-aedc-ce725ef131a8@ispras.ru> <878rdtfmdw.fsf@mid.deneb.enyo.de> Date: Tue, 16 May 2023 10:55:55 +0200 In-Reply-To: (Michael Matz's message of "Mon, 15 May 2023 12:51:26 +0000 (UTC)") Message-ID: <87ilcs64f8.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.9 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-4.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_NUMSUBJECT,KAM_SHORT,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: * Michael Matz: > Hello, > > On Fri, 12 May 2023, Florian Weimer wrote: > >> * Alexander Monakov: >> >> > This is not valid (constraint violation): >> > >> > unsigned x; >> > >> > int *p = &x; >> > >> > In GCC this is diagnosed under -Wpointer-sign: >> > >> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25892 >> >> Thanks for the reference. I filed: >> >> -Wpointer-sign must be enabled by default >> > > Can you please not extend the scope of your proposals in this thread but > create a new one? I understood Joseph as asking for exploring a broadened scope, so I looked into that. > (FWIW: no, this should not be an error, a warning is fine, and I actually > think the current state of it not being in Wall is the right thing as > well) I don't understand why we do not warn by default and warn with -Wall. I would expect this to be either a documented extension (no warning with -Wall), or a warning by default (because it's a conformance issue). Is there any conformance issue that is treated in the same way? Thanks, Florian