Received: by 2002:a05:6358:1087:b0:cb:c9d3:cd90 with SMTP id j7csp1173001rwi; Thu, 13 Oct 2022 09:59:02 -0700 (PDT) X-Google-Smtp-Source: AMsMyM7cVyVtvddJ8xRP3NjW0RUMAefbgBcwTZzmSWTfCShaw6/TX9ArDr0hF4VN00caPADZktVp X-Received: by 2002:aa7:c642:0:b0:458:e065:105b with SMTP id z2-20020aa7c642000000b00458e065105bmr623725edr.354.1665680342298; Thu, 13 Oct 2022 09:59:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1665680342; cv=none; d=google.com; s=arc-20160816; b=XSUf2vRUAy8eJMPM+R3cQU/2SSEtIwVinivev6CYofQJGwfaIKgzZXRc/qPNV2rkC0 0oR9e6SuvzhQDM9IdXR7BqEDNPujEle7j6HQ4tC6mvSuP2G6P7aTERH0kpP482YmWOBN TqSbZxyl1FHuwz7lPsjspfZct3V6R/VuWk51qjCY7k7dVuVmDNedgZV4kEWudt385p33 IA9eHRZXw58PHTxjEBa4wZC+uRxnPSGeVBJ+e5IDkR6azyIHKbar52dCnoncpOC7p62Q Iu9zSp9+i0wQSx/aJHRmtiKjG1fMJTHUD1lMy40Q2Ayr6dKF27Unj25rS7pGagm3q/cc KQwQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=B2fB+em5U2eEHVsnV+waJ7nSYU121NU2Fiq+10JkGPQ=; b=jxmMTxbY5Xx56jtvw/vm6wcPD27R6MzsLpndU6fjCKnlHnIWNQ9h011Jn3cmt3nZG0 HWasE5W0nw0hD8xPbNY1zlWKyfJxZazjR4kK5+hItRddVTfO+8JjF+9QpJVamCDuTH9w ChRAFXqpBn8vo3HNuszu6yunqKYvlxI7rBJcyt0vGTUDaKQIeui84hNORiaTpA5Ev/HL n7fiimi5uGvG4olLnnTt5T2OU3vwC7VUeH7GgCNJzLya34kNzKlOQYbEPY072bSuekYo Utiu0AhmLcH4lf24y/9aXFoFNwqv6XRFhODkL6aJXPiSbIp5BMJSYIbs0B1z4z2Fe+PA /uhw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id qo13-20020a170907212d00b0078dd0fb7a46si126884ejb.427.2022.10.13.09.58.35; Thu, 13 Oct 2022 09:59:02 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229513AbiJMQwJ (ORCPT + 99 others); Thu, 13 Oct 2022 12:52:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34506 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229862AbiJMQwG (ORCPT ); Thu, 13 Oct 2022 12:52:06 -0400 Received: from 1wt.eu (wtarreau.pck.nerim.net [62.212.114.60]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 28E0CB03E9; Thu, 13 Oct 2022 09:52:03 -0700 (PDT) Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id 29DGptkO018919; Thu, 13 Oct 2022 18:51:55 +0200 Date: Thu, 13 Oct 2022 18:51:55 +0200 From: Willy Tarreau To: "Jason A. Donenfeld" Cc: Mark Brown , linux-toolchains@vger.kernel.org, Linux Kbuild mailing list , LKML Subject: Re: gcc 5 & 6 & others already out of date? Message-ID: <20221013165155.GJ16609@1wt.eu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS, SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Oct 13, 2022 at 10:37:21AM -0600, Jason A. Donenfeld wrote: > 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? Ideally we should support at the very least those of the oldest supported LTS kernels, because one thing for LTS users is that we also want to encourage them to try new kernels, and if they can't build newer kernels from the start we all know they'll give up very quickly. And this eases the backport to those kernels as it is expected that a mainline fix will support those versions (even if it may break from time to time by accident, but the intent is there). > 3 years seems like a fairly long amount of time. For a developer changing their distro every 6 months, possibly. Not for users who took time to stabilize their system to something working and who are curious about what the new kernel provides from time to time. Willy