[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAK8P3a2+VC4oNU_DjLrBnB8YhWtU5vee5aGfNgtOrNw=-smWWw@mail.gmail.com>
Date: Wed, 20 Jan 2021 09:08:52 +0100
From: Arnd Bergmann <arnd@...nel.org>
To: Nathan Chancellor <natechancellor@...il.com>
Cc: Nick Desaulniers <ndesaulniers@...gle.com>,
Will Deacon <will@...nel.org>,
Greg KH <gregkh@...uxfoundation.org>,
"# 3.4.x" <stable@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Russell King <linux@...linux.org.uk>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"Theodore Ts'o" <tytso@....edu>,
Florian Weimer <fweimer@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Catalin Marinas <catalin.marinas@....com>,
Caroline Tice <cmtice@...gle.com>,
Luis Lozano <llozano@...gle.com>,
Stephen Hines <srhines@...gle.com>
Subject: Re: [STABLE BACKPORT 4.4.y, 4.9.y and 4.14.y] compiler.h: Raise
minimum version of GCC to 5.1 for arm64
On Wed, Jan 20, 2021 at 12:29 AM Nathan Chancellor
<natechancellor@...il.com> wrote:
> On Tue, Jan 19, 2021 at 02:15:43PM -0800, Nick Desaulniers wrote:
> >
> > Merging this from stable into "Android Common Kernel" trees that were
> > built with AOSP GCC 4.9, I expect this to break some builds. Arnd,
> > IIRC did you mention that AOSP GCC had picked up a fix? If so, did
> > you verify that via disassembly, or gerrit patch file?
The only information I had was the fact that the gcc bug tracker
mentioned it being picked up into the Android gcc and gcc-linaro.
I verified that it was present in gcc-linaro, but did not also check
the Android sources.
> If so, it looks like that patch was picked up in this commit.
>
> https://android.googlesource.com/toolchain/gcc/+/5ae0308a147ec3f6502fd321860524e634a647a6
Right.
Arnd
Powered by blists - more mailing lists