diff options
author | Roland Hieber <rhi@pengutronix.de> | 2020-08-30 23:32:02 +0200 |
---|---|---|
committer | Robert Schwebel <r.schwebel@pengutronix.de> | 2020-08-31 06:53:32 +0200 |
commit | dcf186937fd6192fbd1a0ab1611462f9490e2f73 (patch) | |
tree | 6b1d363e894ae809dbe8e542754a5250ad714cc2 /configs/platform-v8a/platformconfig | |
parent | 35fb9cc4b285511cdeb66f22e7503551dca093b5 (diff) | |
download | DistroKit-dcf186937fd6192fbd1a0ab1611462f9490e2f73.tar.gz DistroKit-dcf186937fd6192fbd1a0ab1611462f9490e2f73.tar.xz |
v8a: update to OSELAS.Toolchain 2020.08.0
Update to the latest toolchain, which was released this week.
Updating to GCC 10 prompts for new kernel options:
| CONFIG_ARM64_PTR_AUTH:
|
| Pointer authentication (part of the ARMv8.3 Extensions) provides
| instructions for signing and authenticating pointers against secret
| keys, which can be used to mitigate Return Oriented Programming (ROP)
| and other attacks.
|
| This option enables these instructions at EL0 (i.e. for userspace).
| Choosing this option will cause the kernel to initialise secret keys
| for each process at exec() time, with these keys being
| context-switched along with the process.
|
| If the compiler supports the -mbranch-protection or
| -msign-return-address flag (e.g. GCC 7 or later), then this option
| will also cause the kernel itself to be compiled with return address
| protection. In this case, and if the target hardware is known to
| support pointer authentication, then CONFIG_STACKPROTECTOR can be
| disabled with minimal loss of protection.
|
| The feature is detected at runtime. If the feature is not present in
| hardware it will not be advertised to userspace/KVM guest nor will it
| be enabled. However, KVM guest also require VHE mode and hence
| CONFIG_ARM64_VHE=y option to use this feature.
|
| If the feature is present on the boot CPU but not on a late CPU, then
| the late CPU will be parked. Also, if the boot CPU does not have
| address auth and the late CPU has then the late CPU will still boot
| but with the feature disabled. On such a system, this option should
| not be selected.
|
| This feature works with FUNCTION_GRAPH_TRACER option only if
| DYNAMIC_FTRACE_WITH_REGS is enabled.
| CONFIG_ARM64_BTI_KERNEL:
|
| Build the kernel with Branch Target Identification annotations
| and enable enforcement of this for kernel code. When this option
| is enabled and the system supports BTI all kernel code including
| modular code must have BTI enabled.
Use their default values for enhanced security.
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
Diffstat (limited to 'configs/platform-v8a/platformconfig')
-rw-r--r-- | configs/platform-v8a/platformconfig | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/configs/platform-v8a/platformconfig b/configs/platform-v8a/platformconfig index 32e0845..4a929a0 100644 --- a/configs/platform-v8a/platformconfig +++ b/configs/platform-v8a/platformconfig @@ -61,11 +61,11 @@ PTXCONF_SYSROOT_CROSS="${PTXDIST_PLATFORMDIR}/sysroot-cross" # # toolchain # -PTXCONF_CROSSCHAIN_VENDOR="OSELAS.Toolchain-2019.09" -PTXCONF_CROSSCHAIN_CHECK="9.2.1" +PTXCONF_CROSSCHAIN_VENDOR="OSELAS.Toolchain-2020.08" +PTXCONF_CROSSCHAIN_CHECK="10.2.1" PTXCONF_LIBC_GLIBC=y # PTXCONF_LIBC_UCLIBC is not set -PTXCONF_GLIBC_VERSION="2.30" +PTXCONF_GLIBC_VERSION="2.32" PTXCONF_GNU_TARGET="aarch64-v8a-linux-gnu" PTXCONF_COMPILER_PREFIX="${PTXCONF_GNU_TARGET}-" PTXCONF_COMPILER_PREFIX_KERNEL="${PTXCONF_COMPILER_PREFIX}" |