c-std-porting.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Paul Wise <pabs@debian.org>
To: debian-devel@lists.debian.org, debian-gcc@lists.debian.org,
Subject: Re: RFC: More C errors by default in GCC 14 (no more implicit function declarations etc.)
Date: Wed, 19 Apr 2023 08:25:19 +0800	[thread overview]
Message-ID: <95f7777d83382f5cf7701e0e8e6bbe9b1698778a.camel@debian.org> (raw)
In-Reply-To: <87y1mpe11q.fsf@oldenburg.str.redhat.com>

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

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?

> 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.

The reproducible builds fuzzing tests get 96.2% reproducible,
this would only go up when not varying most of the fuzzed things.


The existing documentation for Debian archive rebuilds is outdated and
deleted, but Lucas Nusbaum and others have been doing them for a while.




[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2023-04-19  0:25 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 [this message]
2023-04-19  1:14   ` Arsen Arsenović
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=95f7777d83382f5cf7701e0e8e6bbe9b1698778a.camel@debian.org \
    --to=pabs@debian.org \
    --cc=c-std-porting@lists.linux.dev \
    --cc=debian-devel@lists.debian.org \
    --cc=debian-gcc@lists.debian.org \


* 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).