From c91b8aa7cdb50206e9d8fe2fac0c6c4d4f934dae Mon Sep 17 00:00:00 2001 From: vanhofen Date: Sat, 4 Jan 2020 23:55:53 +0100 Subject: [PATCH] - kernel: add support for gcc8 and gcc9 --- make/linux-kernel.mk | 4 ++ .../3_14_kernel-add-support-for-gcc9.patch | 67 +++++++++++++++++++ .../3_9_kernel-add-support-for-gcc8.patch | 67 +++++++++++++++++++ .../3_9_kernel-add-support-for-gcc9.patch | 67 +++++++++++++++++++ .../4_1_kernel-add-support-for-gcc9.patch | 67 +++++++++++++++++++ 5 files changed, 272 insertions(+) create mode 100644 patches/kernel/vuplus/3_14_kernel-add-support-for-gcc9.patch create mode 100644 patches/kernel/vuplus/3_9_kernel-add-support-for-gcc8.patch create mode 100644 patches/kernel/vuplus/3_9_kernel-add-support-for-gcc9.patch create mode 100644 patches/kernel/vuplus/4_1_kernel-add-support-for-gcc9.patch diff --git a/make/linux-kernel.mk b/make/linux-kernel.mk index baddfcde..4a3f7f1a 100644 --- a/make/linux-kernel.mk +++ b/make/linux-kernel.mk @@ -48,6 +48,8 @@ VUPLUS_3_9_PATCH = \ vuplus/3_9_kernel-add-support-for-gcc5.patch \ vuplus/3_9_kernel-add-support-for-gcc6.patch \ vuplus/3_9_kernel-add-support-for-gcc7.patch \ + vuplus/3_9_kernel-add-support-for-gcc8.patch \ + vuplus/3_9_kernel-add-support-for-gcc9.patch \ vuplus/3_9_linux-3.9-gcc-4.9.3-build-error-fixed.patch \ vuplus/3_9_linux-sata_bcm.patch \ vuplus/3_9_mxl5007t-add-no_probe-and-no_reset-parameters.patch \ @@ -70,6 +72,7 @@ VUPLUS_3_14_PATCH = \ vuplus/3_14_kernel-add-support-for-gcc6.patch \ vuplus/3_14_kernel-add-support-for-gcc7.patch \ vuplus/3_14_kernel-add-support-for-gcc8.patch \ + vuplus/3_14_kernel-add-support-for-gcc9.patch \ vuplus/3_14_0001-Support-TBS-USB-drivers.patch \ vuplus/3_14_0001-STV-Add-PLS-support.patch \ vuplus/3_14_0001-STV-Add-SNR-Signal-report-parameters.patch \ @@ -117,6 +120,7 @@ VUPLUS_4_1_PATCH = \ vuplus/4_1_kernel-add-support-for-gcc6.patch \ vuplus/4_1_kernel-add-support-for-gcc7.patch \ vuplus/4_1_kernel-add-support-for-gcc8.patch \ + vuplus/4_1_kernel-add-support-for-gcc9.patch \ vuplus/4_1_0001-Support-TBS-USB-drivers-for-4.1-kernel.patch \ vuplus/4_1_0001-TBS-fixes-for-4.1-kernel.patch \ vuplus/4_1_0001-STV-Add-PLS-support.patch \ diff --git a/patches/kernel/vuplus/3_14_kernel-add-support-for-gcc9.patch b/patches/kernel/vuplus/3_14_kernel-add-support-for-gcc9.patch new file mode 100644 index 00000000..acd4f3fb --- /dev/null +++ b/patches/kernel/vuplus/3_14_kernel-add-support-for-gcc9.patch @@ -0,0 +1,67 @@ +diff --git a/include/linux/compiler-gcc9.h b/include/linux/compiler-gcc9.h +new file mode 100644 +index 0000000..ba064fa +--- /dev/null ++++ b/include/linux/compiler-gcc9.h +@@ -0,0 +1,59 @@ ++#ifndef __LINUX_COMPILER_H ++#error "Please don't include directly, include instead." ++#endif ++ ++#define __used __attribute__((__used__)) ++#define __must_check __attribute__((warn_unused_result)) ++#define __compiler_offsetof(a, b) __builtin_offsetof(a, b) ++ ++/* Mark functions as cold. gcc will assume any path leading to a call ++ to them will be unlikely. This means a lot of manual unlikely()s ++ are unnecessary now for any paths leading to the usual suspects ++ like BUG(), printk(), panic() etc. [but let's keep them for now for ++ older compilers] ++ ++ gcc also has a __attribute__((__hot__)) to move hot functions into ++ a special section, but I don't see any sense in this right now in ++ the kernel context */ ++#define __cold __attribute__((__cold__)) ++ ++#define __UNIQUE_ID(prefix) __PASTE(__PASTE(__UNIQUE_ID_, prefix), __COUNTER__) ++ ++#ifndef __CHECKER__ ++# define __compiletime_warning(message) __attribute__((warning(message))) ++# define __compiletime_error(message) __attribute__((error(message))) ++#endif /* __CHECKER__ */ ++ ++/* ++ * Mark a position in code as unreachable. This can be used to ++ * suppress control flow warnings after asm blocks that transfer ++ * control elsewhere. ++ */ ++#define unreachable() __builtin_unreachable() ++ ++/* Mark a function definition as prohibited from being cloned. */ ++#define __noclone __attribute__((__noclone__)) ++ ++/* ++ * Tell the optimizer that something else uses this function or variable. ++ */ ++#define __visible __attribute__((externally_visible)) ++ ++/* ++ * GCC 'asm goto' miscompiles certain code sequences: ++ * ++ * http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58670 ++ * ++ * Work it around via a compiler barrier quirk suggested by Jakub Jelinek. ++ * ++ * (asm goto is automatically volatile - the naming reflects this.) ++ */ ++#define asm_volatile_goto(x...) do { asm goto(x); asm (""); } while (0) ++ ++#ifdef CONFIG_ARCH_USE_BUILTIN_BSWAP ++#define __HAVE_BUILTIN_BSWAP32__ ++#define __HAVE_BUILTIN_BSWAP64__ ++#define __HAVE_BUILTIN_BSWAP16__ ++#endif /* CONFIG_ARCH_USE_BUILTIN_BSWAP */ ++ ++#define KASAN_ABI_VERSION 6 +-- +2.1.0 diff --git a/patches/kernel/vuplus/3_9_kernel-add-support-for-gcc8.patch b/patches/kernel/vuplus/3_9_kernel-add-support-for-gcc8.patch new file mode 100644 index 00000000..133ae0d7 --- /dev/null +++ b/patches/kernel/vuplus/3_9_kernel-add-support-for-gcc8.patch @@ -0,0 +1,67 @@ +diff --git a/include/linux/compiler-gcc8.h b/include/linux/compiler-gcc8.h +new file mode 100644 +index 0000000..ba064fa +--- /dev/null ++++ b/include/linux/compiler-gcc8.h +@@ -0,0 +1,59 @@ ++#ifndef __LINUX_COMPILER_H ++#error "Please don't include directly, include instead." ++#endif ++ ++#define __used __attribute__((__used__)) ++#define __must_check __attribute__((warn_unused_result)) ++#define __compiler_offsetof(a, b) __builtin_offsetof(a, b) ++ ++/* Mark functions as cold. gcc will assume any path leading to a call ++ to them will be unlikely. This means a lot of manual unlikely()s ++ are unnecessary now for any paths leading to the usual suspects ++ like BUG(), printk(), panic() etc. [but let's keep them for now for ++ older compilers] ++ ++ gcc also has a __attribute__((__hot__)) to move hot functions into ++ a special section, but I don't see any sense in this right now in ++ the kernel context */ ++#define __cold __attribute__((__cold__)) ++ ++#define __UNIQUE_ID(prefix) __PASTE(__PASTE(__UNIQUE_ID_, prefix), __COUNTER__) ++ ++#ifndef __CHECKER__ ++# define __compiletime_warning(message) __attribute__((warning(message))) ++# define __compiletime_error(message) __attribute__((error(message))) ++#endif /* __CHECKER__ */ ++ ++/* ++ * Mark a position in code as unreachable. This can be used to ++ * suppress control flow warnings after asm blocks that transfer ++ * control elsewhere. ++ */ ++#define unreachable() __builtin_unreachable() ++ ++/* Mark a function definition as prohibited from being cloned. */ ++#define __noclone __attribute__((__noclone__)) ++ ++/* ++ * Tell the optimizer that something else uses this function or variable. ++ */ ++#define __visible __attribute__((externally_visible)) ++ ++/* ++ * GCC 'asm goto' miscompiles certain code sequences: ++ * ++ * http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58670 ++ * ++ * Work it around via a compiler barrier quirk suggested by Jakub Jelinek. ++ * ++ * (asm goto is automatically volatile - the naming reflects this.) ++ */ ++#define asm_volatile_goto(x...) do { asm goto(x); asm (""); } while (0) ++ ++#ifdef CONFIG_ARCH_USE_BUILTIN_BSWAP ++#define __HAVE_BUILTIN_BSWAP32__ ++#define __HAVE_BUILTIN_BSWAP64__ ++#define __HAVE_BUILTIN_BSWAP16__ ++#endif /* CONFIG_ARCH_USE_BUILTIN_BSWAP */ ++ ++#define KASAN_ABI_VERSION 4 +-- +2.1.0 diff --git a/patches/kernel/vuplus/3_9_kernel-add-support-for-gcc9.patch b/patches/kernel/vuplus/3_9_kernel-add-support-for-gcc9.patch new file mode 100644 index 00000000..acd4f3fb --- /dev/null +++ b/patches/kernel/vuplus/3_9_kernel-add-support-for-gcc9.patch @@ -0,0 +1,67 @@ +diff --git a/include/linux/compiler-gcc9.h b/include/linux/compiler-gcc9.h +new file mode 100644 +index 0000000..ba064fa +--- /dev/null ++++ b/include/linux/compiler-gcc9.h +@@ -0,0 +1,59 @@ ++#ifndef __LINUX_COMPILER_H ++#error "Please don't include directly, include instead." ++#endif ++ ++#define __used __attribute__((__used__)) ++#define __must_check __attribute__((warn_unused_result)) ++#define __compiler_offsetof(a, b) __builtin_offsetof(a, b) ++ ++/* Mark functions as cold. gcc will assume any path leading to a call ++ to them will be unlikely. This means a lot of manual unlikely()s ++ are unnecessary now for any paths leading to the usual suspects ++ like BUG(), printk(), panic() etc. [but let's keep them for now for ++ older compilers] ++ ++ gcc also has a __attribute__((__hot__)) to move hot functions into ++ a special section, but I don't see any sense in this right now in ++ the kernel context */ ++#define __cold __attribute__((__cold__)) ++ ++#define __UNIQUE_ID(prefix) __PASTE(__PASTE(__UNIQUE_ID_, prefix), __COUNTER__) ++ ++#ifndef __CHECKER__ ++# define __compiletime_warning(message) __attribute__((warning(message))) ++# define __compiletime_error(message) __attribute__((error(message))) ++#endif /* __CHECKER__ */ ++ ++/* ++ * Mark a position in code as unreachable. This can be used to ++ * suppress control flow warnings after asm blocks that transfer ++ * control elsewhere. ++ */ ++#define unreachable() __builtin_unreachable() ++ ++/* Mark a function definition as prohibited from being cloned. */ ++#define __noclone __attribute__((__noclone__)) ++ ++/* ++ * Tell the optimizer that something else uses this function or variable. ++ */ ++#define __visible __attribute__((externally_visible)) ++ ++/* ++ * GCC 'asm goto' miscompiles certain code sequences: ++ * ++ * http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58670 ++ * ++ * Work it around via a compiler barrier quirk suggested by Jakub Jelinek. ++ * ++ * (asm goto is automatically volatile - the naming reflects this.) ++ */ ++#define asm_volatile_goto(x...) do { asm goto(x); asm (""); } while (0) ++ ++#ifdef CONFIG_ARCH_USE_BUILTIN_BSWAP ++#define __HAVE_BUILTIN_BSWAP32__ ++#define __HAVE_BUILTIN_BSWAP64__ ++#define __HAVE_BUILTIN_BSWAP16__ ++#endif /* CONFIG_ARCH_USE_BUILTIN_BSWAP */ ++ ++#define KASAN_ABI_VERSION 6 +-- +2.1.0 diff --git a/patches/kernel/vuplus/4_1_kernel-add-support-for-gcc9.patch b/patches/kernel/vuplus/4_1_kernel-add-support-for-gcc9.patch new file mode 100644 index 00000000..acd4f3fb --- /dev/null +++ b/patches/kernel/vuplus/4_1_kernel-add-support-for-gcc9.patch @@ -0,0 +1,67 @@ +diff --git a/include/linux/compiler-gcc9.h b/include/linux/compiler-gcc9.h +new file mode 100644 +index 0000000..ba064fa +--- /dev/null ++++ b/include/linux/compiler-gcc9.h +@@ -0,0 +1,59 @@ ++#ifndef __LINUX_COMPILER_H ++#error "Please don't include directly, include instead." ++#endif ++ ++#define __used __attribute__((__used__)) ++#define __must_check __attribute__((warn_unused_result)) ++#define __compiler_offsetof(a, b) __builtin_offsetof(a, b) ++ ++/* Mark functions as cold. gcc will assume any path leading to a call ++ to them will be unlikely. This means a lot of manual unlikely()s ++ are unnecessary now for any paths leading to the usual suspects ++ like BUG(), printk(), panic() etc. [but let's keep them for now for ++ older compilers] ++ ++ gcc also has a __attribute__((__hot__)) to move hot functions into ++ a special section, but I don't see any sense in this right now in ++ the kernel context */ ++#define __cold __attribute__((__cold__)) ++ ++#define __UNIQUE_ID(prefix) __PASTE(__PASTE(__UNIQUE_ID_, prefix), __COUNTER__) ++ ++#ifndef __CHECKER__ ++# define __compiletime_warning(message) __attribute__((warning(message))) ++# define __compiletime_error(message) __attribute__((error(message))) ++#endif /* __CHECKER__ */ ++ ++/* ++ * Mark a position in code as unreachable. This can be used to ++ * suppress control flow warnings after asm blocks that transfer ++ * control elsewhere. ++ */ ++#define unreachable() __builtin_unreachable() ++ ++/* Mark a function definition as prohibited from being cloned. */ ++#define __noclone __attribute__((__noclone__)) ++ ++/* ++ * Tell the optimizer that something else uses this function or variable. ++ */ ++#define __visible __attribute__((externally_visible)) ++ ++/* ++ * GCC 'asm goto' miscompiles certain code sequences: ++ * ++ * http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58670 ++ * ++ * Work it around via a compiler barrier quirk suggested by Jakub Jelinek. ++ * ++ * (asm goto is automatically volatile - the naming reflects this.) ++ */ ++#define asm_volatile_goto(x...) do { asm goto(x); asm (""); } while (0) ++ ++#ifdef CONFIG_ARCH_USE_BUILTIN_BSWAP ++#define __HAVE_BUILTIN_BSWAP32__ ++#define __HAVE_BUILTIN_BSWAP64__ ++#define __HAVE_BUILTIN_BSWAP16__ ++#endif /* CONFIG_ARCH_USE_BUILTIN_BSWAP */ ++ ++#define KASAN_ABI_VERSION 6 +-- +2.1.0