From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3282E17D4 for ; Wed, 19 Apr 2023 04:12:03 +0000 (UTC) References: <87y1mpe11q.fsf@oldenburg.str.redhat.com> User-agent: mu4e 1.10.2; emacs 29.0.90 From: Sam James To: Oskari Pirhonen Cc: Florian Weimer , debian-devel@lists.debian.org, debian-gcc@lists.debian.org, c-std-porting@lists.linux.dev Subject: Re: RFC: More C errors by default in GCC 14 (no more implicit function declarations etc.) Date: Wed, 19 Apr 2023 05:10:18 +0100 In-reply-to: Message-ID: <87wn287bpl.fsf@gentoo.org> Precedence: bulk X-Mailing-List: c-std-porting@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Oskari Pirhonen writes: > [[PGP Signed Part:Undecided]] > On Tue, Apr 18, 2023 at 16:07:45 +0200, Florian Weimer wrote: >> Gentoo has been fixing various packages for building with Clang, which >> covers a superset of the issues that need to be addressed: >>=20 >> [TRACKER] Support LLVM/Clang as alternative system compiler=20 >> >>=20 >> IIRC, Gentoo has its own mechanism to detect silent build breakage, but >> I think it's mostly focused on autoconf, so it's less comprehensive, and >> also fixes the stuff that is actually relevant to the distribution. >>=20 > > For Gentoo, I wrote (with some help from others) this QA check [1] which > Portage uses to scan Autoconf, CMake, and Meson config logs for implicit > function declarations. It's inspired by a similar bit of code from the > Macports folks [2] and written with both Clang and GCC in mind. > > It should be possible to adapt for use by others if you feed it the > right dirs and replace a few functions (`has` and `eqa*` OTTOMH) since > nothing about the core logic is Portage-specific. > > Although not so much for silent failures, but maybe still useful for > someone, there's also this QA check [3] which is used to detect other > warnings at build-time. Note for others: this is distinct from the initial approach we took (and are still using) with compiler wrapping and diffing old/new config.log which Florian was referring to. > > - Oskari > best, sam --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iOUEARYKAI0WIQQlpruI3Zt2TGtVQcJzhAn1IN+RkAUCZD9p9l8UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0MjVB NkJCODhERDlCNzY0QzZCNTU0MUMyNzM4NDA5RjUyMERGOTE5MA8cc2FtQGdlbnRv by5vcmcACgkQc4QJ9SDfkZBnzQD9HeTBbjCP79iBVKULhTqDH6Ad/iRMJ+ZmQ2fV XHRUuPYA/jiA0DXUaolvFdZ9JwliT5b6QTkm9dhnbMoTJmFd/R0L =V2En -----END PGP SIGNATURE----- --=-=-=--