linux-kernel - Re: gcc 5 & 6 & others already out of date?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Y0g+wTTJmlaFVLzr@zx2c4.com>
Date:   Thu, 13 Oct 2022 10:37:21 -0600
From:   "Jason A. Donenfeld" <Jason@...c4.com>
To:     Mark Brown <broonie@...nel.org>
Cc:     linux-toolchains@...r.kernel.org,
        Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: gcc 5 & 6 & others already out of date?

On Thu, Oct 13, 2022 at 05:26:04PM +0100, Mark Brown wrote:
> Note that I'm not saying we shouldn't upgrade our requirements at all,
> just that I'm worrying about going from one extreme to the other in
> terms of version requirements - it feels like there's a step change when
> you move from things you can get in current release distros people are
> likely to be using to things that will require a large proportion of
> people to install extra stuff.  At the minute we're more at the other
> end where it can be hard to figure out who'd even have the oldest
> versions we support without deliberately seeking them out and keeping
> them going is noticably making work for people.

Regarding "one extreme to the other", I suspect that in spite of my
arguments, which would seem to justify an extreme, the actual thing I
suggested is a bit more moderate: let's support the latest 2 or 3 gccs
at the time of kernel release. If we choose 3, that's roughly 3 years of
gccs, right? 3 years seems like a fairly long amount of time.

Jason