[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wjHTpG+gMx9vqrZgo8Uw0NqA2kNjS87o63Zv3=WG2K3zA@mail.gmail.com>
Date: Thu, 14 Jan 2021 10:43:07 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Ard Biesheuvel <ardb@...nel.org>
Cc: Russell King - ARM Linux admin <linux@...linux.org.uk>,
Florian Weimer <fweimer@...hat.com>,
Arnd Bergmann <arnd@...nel.org>,
"Cc: Android Kernel" <kernel-team@...roid.com>,
"Theodore Ts'o" <tytso@....edu>,
Peter Zijlstra <peterz@...radead.org>,
Catalin Marinas <catalin.marinas@....com>,
Masahiro Yamada <masahiroy@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Will Deacon <will@...nel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] compiler.h: Raise minimum version of GCC to 5.1 for arm64
On Thu, Jan 14, 2021 at 12:18 AM Ard Biesheuvel <ardb@...nel.org> wrote:
>
> So if the arguments are piling up, what is holding us back, other than
> inertia?
I think we can most certainly just try increasing the minimum version
to 5.1 in the next merge window and see.
> Note that banning 4.9 for arm64 and banning it in general should be
> two different changes in any case, as the former will need to be
> backported to -stable kernels as well.
Yes. The arm64 issue is a clear and known bug, plus I suspect gcc-4.9
is ridiculously old in the arm64 ecosystem anyway.
So the arm64 issue is a bug-fix, the follow-up of just upgrading gcc
requirements in general would be a "keep up with the times, and allow
those variable declarations in loops".
Linus
Powered by blists - more mailing lists