lkml.org 
[lkml]   [2016]   [Feb]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH] kbuild: disable Android-specific compiler features
From
Date
Dne 18.2.2016 v 00:03 Kees Cook napsal(a):
> On Fri, Feb 5, 2016 at 4:44 PM, Kees Cook <keescook@chromium.org> wrote:
>> The Android compilers enable some non-standard features by default. While
>> most Android build systems inject the needed "-mno-android" option via
>> KCFLAGS, it happens too late (at least on x86_64), since KBUILD_CFLAGS
>> gains KCFLAGS after running (and failing) many cc-option tests. (For
>> example, the stack-protector tests happen after arch-specific
>> KBUILD_CFLAGS are added but before the external KCFLAGS are added.) As
>> such, we should notice this option and immediately turn it on as the
>> first cc-option test we run.
>>
>> Signed-off-by: Kees Cook <keescook@chromium.org>
>
> Michal, is this okay? I'd like to get it into -next soon if possible.

Is there a way to detect these compilers and are there some canonical
versions of these? I do not think it's a good idea to add workaround for
each random gcc fork.

Michal

\
 
 \ /
  Last update: 2016-02-18 11:01    [W:0.169 / U:0.252 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site