linux-kernel - Re: [PATCH] Raise the minimum required gcc version to 4.6

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAKwvOdk3Ydp1KtJui3BH=M+wS-m0TywMNzn1BkifumTQWBLS3A@mail.gmail.com>
Date:   Tue, 21 Aug 2018 16:41:46 -0700
From:   Nick Desaulniers <ndesaulniers@...gle.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Masahiro Yamada <yamada.masahiro@...ionext.com>, joe@...ches.com,
        LKML <linux-kernel@...r.kernel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        dave.hansen@...el.com, efault@....de,
        Guenter Roeck <linux@...ck-us.net>,
        Rik van Riel <riel@...riel.com>,
        Kees Cook <keescook@...omium.org>,
        Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org
Subject: Re: [PATCH] Raise the minimum required gcc version to 4.6

On Tue, Aug 21, 2018 at 12:40 PM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> On Mon, Aug 20, 2018 at 11:56 PM Masahiro Yamada
> <yamada.masahiro@...ionext.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