[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKwvOdmLQen+TWF_F3e5-66vtF3FEnoxjEgZbjmOZ9cv6YrEpA@mail.gmail.com>
Date: Tue, 21 Aug 2018 09:32:24 -0700
From: Nick Desaulniers <ndesaulniers@...gle.com>
To: asmadeus@...ewreck.org
Cc: Masahiro Yamada <yamada.masahiro@...ionext.com>,
Kees Cook <keescook@...omium.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
joe@...ches.com, Jonathan Corbet <corbet@....net>,
Arnd Bergmann <arnd@...db.de>, dwmw@...zon.co.uk,
LKML <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Will Deacon <will.deacon@....com>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] compiler-gcc: get back Clang build
On Tue, Aug 21, 2018 at 5:38 AM Dominique Martinet
<asmadeus@...ewreck.org> wrote:
>
> Nick Desaulniers Aug. 21, 2018, 8:09 a.m. UTC:
> > Thanks for noticing, and sending this patch. I'm happy to see others
> > testing with Clang. I noticed this too near the end of the day
> > https://github.com/ClangBuiltLinux/linux/issues/27.
>
> FWIW libbcc so many BPF users also use clang, so this has more impact
> than just testing to build linux with clang (not that this would be any
> reason to delay fixing either way)
>
> I would tend to agree havin a compiler-common + make clang/intel not
> include compiler-gcc would probably be best in the long run but we might
> want a quick fix for 4.19 meanwhile..
That's fair. SOP here is quick (full) revert, then come up with a
better fix. And I do prefer Masahiro's partial revert to a full
revert of Joe's patch. That will give us more time to develop the
proper fix rather than rush. I'll try to see how we can more properly
split the compiler specific headers.
Tested with gcc-7 and clang-8.
Tested-by: Nick Desaulniers <ndesaulniers@...gle.com>
--
Thanks,
~Nick Desaulniers
Powered by blists - more mailing lists