From: Nick Desaulniers <ndesaulniers@google.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
joe@perches.com, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
dave.hansen@intel.com, efault@gmx.de,
Guenter Roeck <linux@roeck-us.net>,
Rik van Riel <riel@surriel.com>,
Kees Cook <keescook@chromium.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] Raise the minimum required gcc version to 4.6
Date: Tue, 21 Aug 2018 16:41:46 -0700 [thread overview]
Message-ID: <CAKwvOdk3Ydp1KtJui3BH=M+wS-m0TywMNzn1BkifumTQWBLS3A@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFxU+cCxLsrTjKdni_xrJ=TvcYbHh0pv7Bk8ns4Gtq8rBA@mail.gmail.com>
On Tue, Aug 21, 2018 at 12:40 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> On Mon, Aug 20, 2018 at 11:56 PM Masahiro Yamada
> <yamada.masahiro@socionext.com> wrote:
> >
> > This broke Clang build.
>
> As mentioned elsewhere, I think the clang build was broken before anyway?
>
> > I sent a patch.
> >
> > https://lore.kernel.org/patchwork/patch/976025/
>
> Yeah, I'd rather just have the clang case have its own file, instead
> of be back in the situation where clang depends on gcc and then has a
> different versioning model so we need to have insane clang version
> tests in the gcc file.
>
> Linus
WIP patch at: https://github.com/ClangBuiltLinux/linux/commit/1f89ae7622c26b8131f42f3a362d6ef41b88a595
Would be happy to get early feedback. Does anyone know who I should
talk to about testing w/ ICC?
--
Thanks,
~Nick Desaulniers
next prev parent reply other threads:[~2018-08-21 23:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 20:15 [PATCH] Raise the minimum required gcc version to 4.6 Joe Perches
2018-08-20 20:25 ` Nick Desaulniers
2018-08-20 20:42 ` Jonathan Corbet
2018-08-20 20:48 ` Joe Perches
2018-08-21 6:55 ` Masahiro Yamada
2018-08-21 19:40 ` Linus Torvalds
2018-08-21 23:41 ` Nick Desaulniers [this message]
2018-08-23 21:52 ` Geert Uytterhoeven
2018-08-23 22:00 ` Nick Desaulniers
2018-08-23 22:00 ` Joe Perches
2018-12-29 14:25 ` Geert Uytterhoeven
2018-12-29 21:57 ` Arnd Bergmann
2019-01-08 14:09 ` Geert Uytterhoeven
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='CAKwvOdk3Ydp1KtJui3BH=M+wS-m0TywMNzn1BkifumTQWBLS3A@mail.gmail.com' \
--to=ndesaulniers@google.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=dave.hansen@intel.com \
--cc=efault@gmx.de \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=riel@surriel.com \
--cc=torvalds@linux-foundation.org \
--cc=yamada.masahiro@socionext.com \
/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).