From: Arnd Bergmann <arnd@kernel.org>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Will Deacon <will@kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
"# 3.4.x" <stable@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Russell King <linux@armlinux.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Theodore Ts'o" <tytso@mit.edu>,
Florian Weimer <fweimer@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Caroline Tice <cmtice@google.com>,
Luis Lozano <llozano@google.com>,
Stephen Hines <srhines@google.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
Date: Wed, 20 Jan 2021 09:08:52 +0100 [thread overview]
Message-ID: <CAK8P3a2+VC4oNU_DjLrBnB8YhWtU5vee5aGfNgtOrNw=-smWWw@mail.gmail.com> (raw)
In-Reply-To: <20210119232952.GA2650682@ubuntu-m3-large-x86>
On Wed, Jan 20, 2021 at 12:29 AM Nathan Chancellor
<natechancellor@gmail.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
prev parent reply other threads:[~2021-01-20 8:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 13:54 [STABLE BACKPORT 4.4.y, 4.9.y and 4.14.y] compiler.h: Raise minimum version of GCC to 5.1 for arm64 Will Deacon
2021-01-19 22:15 ` Nick Desaulniers
2021-01-19 23:29 ` Nathan Chancellor
2021-01-20 8:08 ` Arnd Bergmann [this message]
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='CAK8P3a2+VC4oNU_DjLrBnB8YhWtU5vee5aGfNgtOrNw=-smWWw@mail.gmail.com' \
--to=arnd@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cmtice@google.com \
--cc=fweimer@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=llozano@google.com \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=srhines@google.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--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).