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.129.124]) by sourceware.org (Postfix) with ESMTPS id DEDDE38D50D6 for ; Fri, 21 Oct 2022 19:55:59 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org DEDDE38D50D6 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=1666382159; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=6AcehJcrKEOgLpUFfroqZIWmDsOH/98Wur9ZIJjZpsY=; b=HDP2AHwPJFWDRph8Z1OMURLRdUNvj7rnVAYeSsouToyJWKlornofv3wVfgKlFt4/xK/NB4 RxITL6NPkSJqyCDVjfgPkudVMEl4MICwHbn5jo0eBNPgGiJMOkQkNr/e4CST0k/DLW9ncQ EKR5q1avHVST91OcAylDEPpm2ZPnHf4= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-547-CUB5di8QMFqvotpuRvZBRQ-1; Fri, 21 Oct 2022 15:55:56 -0400 X-MC-Unique: CUB5di8QMFqvotpuRvZBRQ-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 0D0D9886065; Fri, 21 Oct 2022 19:55:56 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.2.16.74]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 1FBB8C15BA5; Fri, 21 Oct 2022 19:55:54 +0000 (UTC) From: Florian Weimer To: Arsen =?utf-8?Q?Arsenovi=C4=87?= Cc: gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org, Joseph Myers , Marek Polacek Subject: Re: C2x features status References: <874jvx81w2.fsf@oldenburg.str.redhat.com> <7452271.dsUahkEHV4@bstg> Date: Fri, 21 Oct 2022 21:55:53 +0200 In-Reply-To: <7452271.dsUahkEHV4@bstg> ("Arsen =?utf-8?Q?Arsenovi=C4=87=22?= =?utf-8?Q?'s?= message of "Fri, 21 Oct 2022 21:29:24 +0200") Message-ID: <87r0z16jee.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.8 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-4.8 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,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: * Arsen Arsenovi=C4=87: > On Friday, 21 October 2022 21:14:54 CEST Marek Polacek via Gcc wrote: >> commit 0a91bdaf177409a2a5e7895bce4f0e7091b4b3ca >> Author: Joseph Myers >> Date: Wed Sep 7 13:56:25 2022 +0000 >>=20 >> c: New C2x keywords >>=20 >> which says: >>=20 >> As with the removal of unprototyped functions, this change has a >> high risk of breaking some old code and people doing GNU/Linux >> distribution builds may wish to see how much is broken in a build >> with a -std=3Dgnu2x default. > > It already does break a lot. See https://bugs.gentoo.org/870412=20 > (comments go over the details). I was intending on giving this issue a= =20 > proper look in the GNU toolchain frame of reference, but never got=20 > around to it (and I kinda knocked priority down after managing to=20 > configure properly once IIRC). That's the implicit function declaration/implicit int change. This won't happen in GCC 13, it's too late for that. I tried to make this change a couple of years in Fedora, and just flipping the compiler flag Does Not Work. I hope to get there in time for GCC 14. Thank you for sharing the Gentoo tracker. Maybe we can reuse some patches from there and contribute ours. I trust Gentoo aims to upstream patches as they become available? Unfortunately, I expect that a lot of these issues will be in packages that don't have an active upstream anymore, which makes sharing patches more challenging. In other cases, we'll just build with -std=3Dgnu89 (e.g. unzip , it has configure-style checking implemented without autoconf). Thanks, Florian