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  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]
Date:   Tue, 21 Aug 2018 14:38:32 +0200
From:   Dominique Martinet <>
To:     Nick Desaulniers <>,
        Masahiro Yamada <>
Cc:     Kees Cook <>,
        Linus Torvalds <>,
        Joe Perches <>,
        Jonathan Corbet <>,
        Masahiro Yamada <>,
        Arnd Bergmann <>,
        David Woodhouse <>,, Thomas Gleixner <>,
        Will Deacon <>,
        Geert Uytterhoeven <>,
        Ingo Molnar <>,
        Andrew Morton <>
Subject: Re: [PATCH] compiler-gcc: get back Clang build

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

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..

Dominique Martinet

Powered by blists - more mailing lists