From: Sam James <sam@gentoo.org>
To: Oskari Pirhonen <xxc3ncoredxx@gmail.com>
Cc: Florian Weimer <fweimer@redhat.com>,
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 [thread overview]
Message-ID: <87wn287bpl.fsf@gentoo.org> (raw)
In-Reply-To: <ZD9UbrVr6VaU+rbA@dj3ntoo>
[-- Attachment #1: Type: text/plain, Size: 1567 bytes --]
Oskari Pirhonen <xxc3ncoredxx@gmail.com> 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:
>>
>> [TRACKER] Support LLVM/Clang as alternative system compiler
>> <https://bugs.gentoo.org/showdependencytree.cgi?id=408963&hide_resolved=0>
>>
>> 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.
>>
>
> 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]
prev parent reply other threads:[~2023-04-19 4:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 14:07 RFC: More C errors by default in GCC 14 (no more implicit function declarations etc.) Florian Weimer
2023-04-18 22:54 ` G. Branden Robinson
2023-04-18 23:17 ` Guillem Jover
2023-04-19 12:06 ` Florian Weimer
2023-04-19 0:25 ` Paul Wise
2023-04-19 1:14 ` Arsen Arsenović
2023-04-19 2:39 ` Oskari Pirhonen
2023-04-19 4:10 ` Sam James [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wn287bpl.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=c-std-porting@lists.linux.dev \
--cc=debian-devel@lists.debian.org \
--cc=debian-gcc@lists.debian.org \
--cc=fweimer@redhat.com \
--cc=xxc3ncoredxx@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.