c-std-porting.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Arsen Arsenović" <arsen@aarsen.me>
To: 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 03:14:52 +0200	[thread overview]
Message-ID: <86a5z4mzu2.fsf@aarsen.me> (raw)
In-Reply-To: <95f7777d83382f5cf7701e0e8e6bbe9b1698778a.camel@debian.org>

[-- Attachment #1: Type: text/plain, Size: 1501 bytes --]


Paul Wise <pabs@debian.org> writes:

> On Tue, 2023-04-18 at 16:07 +0200, Florian Weimer wrote:
>
>> TL;DR: I want to propose a GCC 14 change which will impact
>> distributions, so I'd like to gather some feedback from Debian.
>
> Is this change being made the upstream defaults?
>
> Or will it be a distro override like the hardening flags are?

The intention is to make this a default, in order to brace people for a
future C default standard version changes.

>> I would appreciate some discussion on the Debian impact.
>
> Since most of the Debian archive can be reproducibly built, it seems
> like the way to gauge the impact of this change on Debian would be to
> do two archive rebuilds, once without the flags and once with the
> flags, then compare the two builds for each package using diffoscope.

This seems reasonable.  I suspect changes largely in configure scripts
based on our prior experience[1].

Have a lovely night.

> The reproducible builds fuzzing tests get 96.2% reproducible,
> this would only go up when not varying most of the fuzzed things.
>
> https://tests.reproducible-builds.org/debian/reproducible.html
>
> The existing documentation for Debian archive rebuilds is outdated and
> deleted, but Lucas Nusbaum and others have been doing them for a while.
>
> https://wiki.debian.org/MassRebuilds
> https://wiki.debian.org/qa.debian.org/ArchiveTesting?action=recall&rev=23

[1] https://bugs.gentoo.org/870412
-- 
Arsen Arsenović

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]

  reply	other threads:[~2023-04-19  1:28 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ć [this message]
2023-04-19  2:39 ` Oskari Pirhonen
2023-04-19  4:10   ` Sam James

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=86a5z4mzu2.fsf@aarsen.me \
    --to=arsen@aarsen.me \
    --cc=c-std-porting@lists.linux.dev \
    --cc=debian-devel@lists.debian.org \
    --cc=debian-gcc@lists.debian.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).