linux-stable.git/Makefile, branch v4.4.166

Linux 4.4.166

2018-12-01T08:46:41+00:00

Linux 4.4.165

2018-11-27T15:08:03+00:00

kbuild: Add __cc-option macro

2018-11-27T15:07:59+00:00

commit 9f3f1fd299768782465cb32cdf0dd4528d11f26b upstream.

cc-option uses KBUILD_CFLAGS and KBUILD_CPPFLAGS when it determines
whether an option is supported or not. This is fine for options used to
build the kernel itself, however some components like the x86 boot code
use a different set of flags.

Add the new macro __cc-option which is a more generic version of
cc-option with additional parameters. One parameter is the compiler
with which the check should be performed, the other the compiler options
to be used instead KBUILD_C*FLAGS.

Refactor cc-option and hostcc-option to use __cc-option and move
hostcc-option to scripts/Kbuild.include.

Suggested-by: Arnd Bergmann 
Suggested-by: Masahiro Yamada 
Signed-off-by: Matthias Kaehlcke 
Acked-by: Arnd Bergmann 
Acked-by: Michal Marek 
Signed-off-by: Masahiro Yamada 
[nc: Fix conflicts due to lack of CC_OPTION_CFLAGS and hostcc-option
     wasn't added until v4.8 so no point including it in this tree]
Signed-off-by: Nathan Chancellor 
Signed-off-by: Greg Kroah-Hartman

kbuild: allow to use GCC toolchain not in Clang search path

2018-11-27T15:07:59+00:00

commit ef8c4ed9db80261f397f0c0bf723684601ae3b52 upstream.

When using a GCC cross toolchain which is not in a compiled in
Clang search path, Clang reverts to the system assembler and
linker. This leads to assembler or linker errors, depending on
which tool is first used for a given architecture.

It seems that Clang is not searching $PATH for a matching
assembler or linker.

Make sure that Clang picks up the correct assembler or linker by
passing the cross compilers bin directory as search path.

This allows to use Clang provided by distributions with GCC
toolchains not in /usr/bin.

Link: https://github.com/ClangBuiltLinux/linux/issues/78
Signed-off-by: Stefan Agner 
Reviewed-and-tested-by: Nick Desaulniers 
Signed-off-by: Masahiro Yamada 
[nc: Adjust context]
Signed-off-by: Nathan Chancellor 
Signed-off-by: Greg Kroah-Hartman

kbuild: set no-integrated-as before incl. arch Makefile

2018-11-27T15:07:59+00:00

commit 0f0e8de334c54c38818a4a5390a39aa09deff5bf upstream.

In order to make sure compiler flag detection for ARM works
correctly the no-integrated-as flags need to be set before
including the arch specific Makefile.

Fixes: cfe17c9bbe6a ("kbuild: move cc-option and cc-disable-warning after incl. arch Makefile")
Signed-off-by: Stefan Agner 
Signed-off-by: Masahiro Yamada 
[nc: Adjust context]
Signed-off-by: Nathan Chancellor 
Signed-off-by: Greg Kroah-Hartman

kbuild: clang: disable unused variable warnings only when constant

2018-11-27T15:07:59+00:00

commit 0a5f41767444cc3b4fc5573921ab914b4f78baaa upstream.

Currently, GCC disables -Wunused-const-variable, but not
-Wunused-variable, so warns unused variables if they are
non-constant.

While, Clang does not warn unused variables at all regardless of
the const qualifier because -Wno-unused-const-variable is implied
by the stronger option -Wno-unused-variable.

Disable -Wunused-const-variable instead of -Wunused-variable so that
GCC and Clang work in the same way.

Signed-off-by: Prasad Sodagudi 
Signed-off-by: Masahiro Yamada 
Signed-off-by: Nathan Chancellor 
Signed-off-by: Greg Kroah-Hartman

kbuild: clang: remove crufty HOSTCFLAGS

2018-11-27T15:07:58+00:00

commit df16aaac26e92e97ab7234d3f93c953466adc4b5 upstream.

When compiling with `make CC=clang HOSTCC=clang`, I was seeing warnings
that clang did not recognize -fno-delete-null-pointer-checks for HOSTCC
targets.  These were added in commit 61163efae020 ("kbuild: LLVMLinux:
Add Kbuild support for building kernel with Clang").

Clang does not support -fno-delete-null-pointer-checks, so adding it to
HOSTCFLAGS if HOSTCC is clang does not make sense.

It's not clear why the other warnings were disabled, and just for
HOSTCFLAGS, but I can remove them, add -Werror to HOSTCFLAGS and compile
with clang just fine.

Suggested-by: Masahiro Yamada 
Signed-off-by: Nick Desaulniers 
Signed-off-by: Masahiro Yamada 
[nc: Adjust context]
Signed-off-by: Nathan Chancellor 
Signed-off-by: Greg Kroah-Hartman

kbuild: clang: fix build failures with sparse check

2018-11-27T15:07:58+00:00

commit bb3f38c3c5b759163e09b9152629cc789731de47 upstream.

We should avoid using the space character when passing arguments to
clang, because static code analysis check tool such as sparse may
misinterpret the arguments followed by spaces as build targets hence
cause the build to fail.

Signed-off-by: David Lin 
Signed-off-by: Masahiro Yamada 
Signed-off-by: Nathan Chancellor 
Signed-off-by: Greg Kroah-Hartman

kbuild: move cc-option and cc-disable-warning after incl. arch Makefile

2018-11-27T15:07:58+00:00

commit cfe17c9bbe6a673fdafdab179c32b355ed447f66 upstream.

Geert reported commit ae6b289a3789 ("kbuild: Set KBUILD_CFLAGS before
incl. arch Makefile") broke cross-compilation using a cross-compiler
that supports less compiler options than the host compiler.

For example,

  cc1: error: unrecognized command line option "-Wno-unused-but-set-variable"

This problem happens on architectures that setup CROSS_COMPILE in their
arch/*/Makefile.

Move the cc-option and cc-disable-warning back to the original position,
but keep the Clang target options untouched.

Fixes: ae6b289a3789 ("kbuild: Set KBUILD_CFLAGS before incl. arch Makefile")
Reported-by: Geert Uytterhoeven 
Signed-off-by: Masahiro Yamada 
Tested-by: Geert Uytterhoeven 
[nc: Adjust context]
Signed-off-by: Nathan Chancellor 
Signed-off-by: Greg Kroah-Hartman

kbuild: Set KBUILD_CFLAGS before incl. arch Makefile

2018-11-27T15:07:58+00:00

commit ae6b289a37890909fea0e4a1666e19377fa0ed2c upstream.

Set the clang KBUILD_CFLAGS up before including arch/ Makefiles,
so that ld-options (etc.) can work correctly.

This fixes errors with clang such as ld-options trying to CC
against your host architecture, but LD trying to link against
your target architecture.

Signed-off-by: Chris Fries 
Signed-off-by: Nick Desaulniers 
Reviewed-by: Matthias Kaehlcke 
Tested-by: Matthias Kaehlcke 
Signed-off-by: Masahiro Yamada 
[nc: Adjust context]
Signed-off-by: Nathan Chancellor 
Signed-off-by: Greg Kroah-Hartman