Received: by 2002:a05:6a10:a852:0:0:0:0 with SMTP id d18csp3666156pxy; Tue, 4 May 2021 07:23:41 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwIhkOPCEmz9UNkoAN0oesZ+EfiLj6VOYp9iumKv9nk1yAXaDKp1M9CXFptks9S8xTTC/TU X-Received: by 2002:a17:90b:249:: with SMTP id fz9mr21099414pjb.162.1620138220906; Tue, 04 May 2021 07:23:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620138220; cv=none; d=google.com; s=arc-20160816; b=QoRAYgD3udZNCYzCUWfsgST3NOHfQNtGG7uVKsXouni7beEgAJgj2bxYSmturmTOVu pHzP0yORtTC6sBFjjIiAzGRMx6l0o6rzlSIIGhKOk89F2DVtjvTDMZNZ9IjzH8tP/YSE /lTnRtJ0Wyiamb7nZvHhGTqcHGzFxzq+f+swuLUGapBLRjQd4eHxprQmcreTd5YY4n2Q VFaCFLyUHyJE275SoX71gbdVSOT4v/hiLtv3g8b2Izp8p5EqsZXaZRmpT3b50/xSyVtb R8YU9Mm6RVmb2yqMF6WY3ecCjGb1ng87h1K/YtHCgRnG/Gb4hdKSjijBhOW3TW0lqlra CxkA== 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-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=eDT+DJZ7O2KfKKhPn1AndeyZ5VeZy+lGlFfTrL/8u4E=; b=wv9I495EQOWuVXGDLvwSF1mCj+0/DeKVvCLCcdDgw3qdYR0XkdFU7g8N4eF7mZh1bz 3J8tZIcLbH9pjpxnzPvviXLrvaaDrjy8Z5NcBk30qO1xnPJ1kA9KyVaoQqez0DuQzGFL rrcqb0ap9MSr3Ik3daMYoBNW+fjTdYno9OLfsga/13dJGKHfwGi4OC548gXk9gUaGsCn NWpPfk/DckRD+AEXSO1US+ns5XPO0y/x3aO7lVEpN0KIfPkTaZPuYdXppershDfso7UV HoRmvLMYFkhPSLGgUSJQYD+LCdc/3ipes0nuKmhOnS1Y7VRFcsFEDvynda3+WJakvkzI riJA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id q134si1911032pfc.204.2021.05.04.07.23.28; Tue, 04 May 2021 07:23:40 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230283AbhEDMSM (ORCPT + 99 others); Tue, 4 May 2021 08:18:12 -0400 Received: from mx2.suse.de ([195.135.220.15]:33668 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230188AbhEDMSL (ORCPT ); Tue, 4 May 2021 08:18:11 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id A0178AE5E; Tue, 4 May 2021 12:17:15 +0000 (UTC) Date: Tue, 4 May 2021 14:17:13 +0200 From: Michal =?iso-8859-1?Q?Such=E1nek?= To: Miguel Ojeda Cc: Ben Dooks , Albert Ou , Arnd Bergmann , Linux Kbuild mailing list , Greg Kroah-Hartman , Masahiro Yamada , Jonathan Corbet , Linux Doc Mailing List , linux-kernel , Miguel Ojeda , Will Deacon , Palmer Dabbelt , Paul Walmsley , Catalin Marinas , Joe Perches , Paul Mackerras , linux-riscv , linuxppc-dev , Linus Torvalds , Linux ARM Subject: Re: [PATCH] Raise the minimum GCC version to 5.2 Message-ID: <20210504121713.GT6564@kitsune.suse.cz> References: <20210501151538.145449-1-masahiroy@kernel.org> <3943bc020f6227c8801907317fc113aa13ad4bad.camel@perches.com> <65cda2bb-1b02-6ebc-0ea2-c48927524aa0@codethink.co.uk> <20210504092225.GS6564@kitsune.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.11.3 (2019-02-01) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 04, 2021 at 02:09:24PM +0200, Miguel Ojeda wrote: > On Tue, May 4, 2021 at 11:22 AM Michal Such?nek wrote: > > > > Except it makes answering the question "Is this bug we see on this > > ancient system still present in upstream?" needlessly more difficult to > > answer. > > Can you please provide some details? If you are talking about testing > a new kernel image in the ancient system "as-is", why wouldn't you > build it in a newer system? If you are talking about particular > problems about bisecting (kernel, compiler) pairs etc., details would > also be welcome. Yes, bisecting comes to mind. If you need to switch the userspace as well the bisection results are not that solid. You may not be even able to bisect because the workload does not exist on a new system at all. Crafting a minimal test case that can be forward-ported to a new system is not always trivial - if you understood the problem to that extent you might not even need to bisect it in the first place. Thanks Michal