linux-toolchains.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-toolchains@vger.kernel.org,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: gcc 5 & 6 & others already out of date?
Date: Thu, 13 Oct 2022 10:37:21 -0600	[thread overview]
Message-ID: <Y0g+wTTJmlaFVLzr@zx2c4.com> (raw)
In-Reply-To: <Y0g8HEYHZYHGdwlf@sirena.org.uk>

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

  reply	other threads:[~2022-10-13 16:37 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
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 [this message]
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

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=Y0g+wTTJmlaFVLzr@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=broonie@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-toolchains@vger.kernel.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).