linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: "Michal Suchánek" <msuchanek@suse.de>,
	"Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>
Cc: Albert Ou <aou@eecs.berkeley.edu>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Joe Perches <joe@perches.com>,
	Ben Dooks <ben.dooks@codethink.co.uk>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Miguel Ojeda <ojeda@kernel.org>,
	Paul Mackerras <paulus@samba.org>,
	linux-riscv <linux-riscv@lists.infradead.org>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Will Deacon <will@kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] Raise the minimum GCC version to 5.2
Date: Tue, 4 May 2021 14:26:18 +0200	[thread overview]
Message-ID: <529aef7c-30b1-f6c5-4610-34bd869e4ad4@csgroup.eu> (raw)
In-Reply-To: <20210504121713.GT6564@kitsune.suse.cz>



Le 04/05/2021 à 14:17, Michal Suchánek a écrit :
> 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 <msuchanek@suse.de> 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.
> 

But you don't need to switch the userspace or the complete build tools to build a kernel with a 
newer toolchain.

All you have to do is take one from https://mirrors.edge.kernel.org/pub/tools/crosstool/

I'm doing everything under CentOS 6, and using one of those tools allows me to build latest kernel 
without breaking anything else.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-05-04 12:28 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-01 15:15 [PATCH] Raise the minimum GCC version to 5.2 Masahiro Yamada
2021-05-01 15:52 ` Miguel Ojeda
2021-05-01 17:38   ` Christophe Leroy
2021-05-02  2:41   ` Joe Perches
2021-05-02 18:30     ` Segher Boessenkool
2021-05-02 20:00       ` Joe Perches
2021-05-02 20:32         ` Segher Boessenkool
2021-05-02 21:05           ` Ali Kaasinen
2021-05-02 21:08           ` Linus Torvalds
2021-05-02 22:30             ` Matthew Wilcox
2021-05-03  7:34               ` Alexander Dahl
2021-05-03  8:54                 ` Joe Perches
2021-05-03  9:25                 ` Arnd Bergmann
2021-05-03 12:20                   ` David Laight
2021-05-03 13:10                     ` Miguel Ojeda
2021-05-04  5:30                   ` Alexander Dahl
2021-05-04  6:33                     ` Christophe Leroy
2021-05-04 12:07                     ` Arnd Bergmann
2021-05-04 13:25                   ` Andy Shevchenko
2021-05-03 11:35               ` Arnd Bergmann
2021-05-03  9:49             ` Kirill A. Shutemov
2021-05-02 21:23           ` Joe Perches
2021-05-03  0:44             ` Segher Boessenkool
2021-05-03  9:57               ` Arnd Bergmann
2021-05-04  7:56     ` Ben Dooks
2021-05-04  8:38       ` Miguel Ojeda
2021-05-04  9:22         ` Michal Suchánek
2021-05-04 12:09           ` Miguel Ojeda
2021-05-04 12:17             ` Michal Suchánek
2021-05-04 12:26               ` Christophe Leroy [this message]
2021-05-02 18:37 ` Segher Boessenkool
2021-05-03  6:16 ` Christophe Leroy
2021-05-04  2:13   ` Masahiro Yamada
2021-05-04 13:18   ` Andy Shevchenko
2021-05-03 12:27 ` David Sterba
2021-05-15  7:14 ` Pavel Machek
2021-05-15  7:27   ` Joe Perches

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=529aef7c-30b1-f6c5-4610-34bd869e4ad4@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=aou@eecs.berkeley.edu \
    --cc=arnd@arndb.de \
    --cc=ben.dooks@codethink.co.uk \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=masahiroy@kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=msuchanek@suse.de \
    --cc=ojeda@kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=paulus@samba.org \
    --cc=torvalds@linux-foundation.org \
    --cc=will@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).