[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKwvOdmhNH4PYNwH+tsZc4uQQJVhOOHSph2YdDCHcyWNyFMxyA@mail.gmail.com>
Date: Fri, 20 Apr 2018 16:43:05 +0000
From: Nick Desaulniers <ndesaulniers@...gle.com>
To: marc.zyngier@....com
Cc: Andrey Konovalov <andreyknvl@...gle.com>,
Christoffer Dall <christoffer.dall@...aro.org>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
linux-arm-kernel@...ts.infradead.org, kvmarm@...ts.cs.columbia.edu,
LKML <linux-kernel@...r.kernel.org>,
Kostya Serebryany <kcc@...gle.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Alexander Potapenko <glider@...gle.com>
Subject: Re: Clang arm64 build is broken
On Fri, Apr 20, 2018 at 9:36 AM Marc Zyngier <marc.zyngier@....com> wrote:
> On 20/04/18 17:30, Nick Desaulniers wrote:
> > On Fri, Apr 20, 2018 at 1:13 AM Marc Zyngier <marc.zyngier@....com>
wrote:
> >> Clang isn't
> >> really supported to build the arm64 kernel anyway
> >
> > Can you expand on this? There are millions of arm64 devices shipping
with
> > Clang built Linux kernels.
> How many of these devices run a full-featured mainline kernel?
> Sure, Android is building the kernel with clang, but that's with a pile
> of out of tree patches. At that point, I'm not sure we're talking about
> the same arm64 kernel.
Do you recommend that we only work with ARM licensed SoC vendors with no
out of tree patches?
--
Thanks,
~Nick Desaulniers
Powered by blists - more mailing lists