From: David Laight <David.Laight@ACULAB.COM>
To: "'Jason A. Donenfeld'" <Jason@zx2c4.com>,
"Linux Kbuild mailing list" <firstname.lastname@example.org>,
Subject: RE: gcc 5 & 6 & others already out of date?
Date: Thu, 13 Oct 2022 12:22:37 +0000 [thread overview]
Message-ID: <8e31925d92e9496dad35290bad1c3dd3@AcuMS.aculab.com> (raw)
From: Jason A. Donenfeld
> Sent: 13 October 2022 02:37
> And then there's old trusty gcc. Gcc also improves according to a nice
> cadence, and we know people are using later gccs because nobody is
> catching the build errors from old gccs. So let's stop pretending we
> support old compilers. We clearly don't. Maybe some subset of code
> does, but by and large, I doubt many developers are actually daily
> driving gcc 5.1 and doing allyesconfig builds with it. Yes, many are
> rightfully cautious of gcc 12 and stick with gcc 11 still, and that's
> reasonable, but 11 or even 10 is still way larger than 5.1.
> The truth is, people tend to use more recent toolchains. And if Clang
> hasn't broken the will of the stranglers, then surely Rust will.
Developers might use recent toolchains, but users are much
more likely to use the one in the distribution they have installed.
Working out how to build a kernel is hard enough.
Requiring non-standard versions of gcc is a PITA.
Remember that you can load a current kernel on quite
There can be all sorts of reasons for wanting to keep building
non-kernel 'stuff' with the default toolchain.
Anyone using clang almost certainly has to download a recent
version - but this is not true of gcc.
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2022-10-13 12:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 1:36 gcc 5 & 6 & others already out of date? Jason A. Donenfeld
2022-10-13 12:22 ` David Laight [this message]
2022-10-13 12:59 ` Mark Brown
2022-10-13 15:23 ` Jason A. Donenfeld
2022-10-13 16:18 ` Willy Tarreau
2022-10-14 4:28 ` David Laight
2022-10-14 5:27 ` Willy Tarreau
2022-10-13 16:26 ` Mark Brown
2022-10-13 16:37 ` Jason A. Donenfeld
2022-10-13 16:51 ` Willy Tarreau
2022-10-13 17:16 ` Mark Brown
2022-10-13 18:38 ` Florian Weimer
2022-10-13 20:23 ` Mark Brown
2022-10-14 6:15 ` Florian Weimer
2022-10-13 18:39 ` Florian Weimer
2022-10-13 21:03 ` Nick Desaulniers
2022-10-14 6:37 ` Florian Weimer
2022-10-13 21:08 ` Nick Desaulniers
2022-10-14 1:31 ` Jason A. Donenfeld
2022-10-14 11:13 ` Mark Brown
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 \
* 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).