patrick/zephyr
1
0
Fork 0
Code Issues Pull requests Actions 8 Packages Projects Releases Wiki Activity
zephyr/cmake/compiler/gcc/target_arm.cmake

61 lines
1.4 KiB
CMake
Raw Normal View History

cmake: compiler: introduce target_arm.cmake Pull ARM flags into cmake/compiler/gcc/target.cmake to be reused between gcc and clang. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2019-09-19 02:41:37 +02:00
# SPDX-License-Identifier: Apache-2.0
cmake/target_arm: Use NO_SPLIT for TOOLCHAIN_LD_FLAGS The whole set of architecture flags must be specified together as they might not make sense in isolation, e.g. -mfloat-abi=hard requires a -mcpu value that might have an FPU. Use the NO_SPLIT feature to bind all of the linker options together so that the linker can compute the correct linker paths for toolchain-provided libraries like libc and libgcc. Signed-off-by: Keith Packard <keithp@keithp.com>
2022-10-21 00:09:50 +02:00
set(ARM_C_FLAGS)
list(APPEND ARM_C_FLAGS -mcpu=${GCC_M_CPU})
arch: arm: aarch64: Force LP64 ABI This commit adds the GCC `-mabi=lp64` flag to force the LP64 (64-bit long and pointer) ABI, which is mandatory for running the Zephyr AArch64 architecture port. Note that this flag is, strictly speaking, not necessary in most cases because the AArch64 GCC defaults to using the LP64 ABI. This flag is required, however, if compiling Zephyr with a GCC that is configured with `--with-abi=ilp32`, which makes ILP32 the default ABI. Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
2020-04-21 09:52:57 +02:00
arm/arm64: Make ARM64 a standalone architecture Split ARM and ARM64 architectures. Details: - CONFIG_ARM64 is decoupled from CONFIG_ARM (not a subset anymore) - Arch and include AArch64 files are in a dedicated directory (arch/arm64 and include/arch/arm64) - AArch64 boards and SoC are moved to soc/arm64 and boards/arm64 - AArch64-specific DTS files are moved to dts/arm64 - The A72 support for the bcm_vk/viper board is moved in the boards/bcm_vk/viper directory Signed-off-by: Carlo Caione <ccaione@baylibre.com>
2021-03-25 11:56:15 +01:00
if(CONFIG_COMPILER_ISA_THUMB2)
cmake/target_arm: Use NO_SPLIT for TOOLCHAIN_LD_FLAGS The whole set of architecture flags must be specified together as they might not make sense in isolation, e.g. -mfloat-abi=hard requires a -mcpu value that might have an FPU. Use the NO_SPLIT feature to bind all of the linker options together so that the linker can compute the correct linker paths for toolchain-provided libraries like libc and libgcc. Signed-off-by: Keith Packard <keithp@keithp.com>
2022-10-21 00:09:50 +02:00
list(APPEND ARM_C_FLAGS -mthumb)
arm/arm64: Make ARM64 a standalone architecture Split ARM and ARM64 architectures. Details: - CONFIG_ARM64 is decoupled from CONFIG_ARM (not a subset anymore) - Arch and include AArch64 files are in a dedicated directory (arch/arm64 and include/arch/arm64) - AArch64 boards and SoC are moved to soc/arm64 and boards/arm64 - AArch64-specific DTS files are moved to dts/arm64 - The A72 support for the bcm_vk/viper board is moved in the boards/bcm_vk/viper directory Signed-off-by: Carlo Caione <ccaione@baylibre.com>
2021-03-25 11:56:15 +01:00
endif()
cmake: compiler: introduce target_arm.cmake Pull ARM flags into cmake/compiler/gcc/target.cmake to be reused between gcc and clang. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2019-09-19 02:41:37 +02:00
cmake/target_arm: Use NO_SPLIT for TOOLCHAIN_LD_FLAGS The whole set of architecture flags must be specified together as they might not make sense in isolation, e.g. -mfloat-abi=hard requires a -mcpu value that might have an FPU. Use the NO_SPLIT feature to bind all of the linker options together so that the linker can compute the correct linker paths for toolchain-provided libraries like libc and libgcc. Signed-off-by: Keith Packard <keithp@keithp.com>
2022-10-21 00:09:50 +02:00
list(APPEND ARM_C_FLAGS -mabi=aapcs)
arch: arm: Remove extraneous root cmake files The ARM architecture root directory contains `aarch32.cmake` and `aarch64.cmake` files whose contents are better suited to go into other more purpose-specific files. This commit removes the aforementioned files and moves their contents to other files following the convention used by other architectures. Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
2020-04-09 11:00:29 +02:00
arm/arm64: Make ARM64 a standalone architecture Split ARM and ARM64 architectures. Details: - CONFIG_ARM64 is decoupled from CONFIG_ARM (not a subset anymore) - Arch and include AArch64 files are in a dedicated directory (arch/arm64 and include/arch/arm64) - AArch64 boards and SoC are moved to soc/arm64 and boards/arm64 - AArch64-specific DTS files are moved to dts/arm64 - The A72 support for the bcm_vk/viper board is moved in the boards/bcm_vk/viper directory Signed-off-by: Carlo Caione <ccaione@baylibre.com>
2021-03-25 11:56:15 +01:00
if(CONFIG_FPU)
cmake/target_arm: Use NO_SPLIT for TOOLCHAIN_LD_FLAGS The whole set of architecture flags must be specified together as they might not make sense in isolation, e.g. -mfloat-abi=hard requires a -mcpu value that might have an FPU. Use the NO_SPLIT feature to bind all of the linker options together so that the linker can compute the correct linker paths for toolchain-provided libraries like libc and libgcc. Signed-off-by: Keith Packard <keithp@keithp.com>
2022-10-21 00:09:50 +02:00
list(APPEND ARM_C_FLAGS -mfpu=${GCC_M_FPU})
cmake: gcc: target_arm: Support advanced floating-point options This commit updates the Zephyr build system to support specifying advanced floating-point compilation options derived from the newly introduced unified floating-point configurations. The following changes are introduced by this commit: 1. Specify architecture floating-point option to the `-mcpu` flag. 2. Specify floating-point unit (FPU) type using the `-mfpu` flag. Note that the `-march` flag is not specified separately because the `-mcpu` flag provides more detailed architecture options and this makes the `-march` flag redundant. Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
2020-03-30 03:10:32 +02:00
arch: introduce config DCLS Some processors support Dual-redundant Core Lock-step DCLS) topology but the processor still can be ran in split-lock mode (by default or changed at flash time). So, introduce config DCLS that is enabled by default if config CPU_HAS_DCLS is set, it should be disabled if processor is used in split-lock mode. Signed-off-by: Dat Nguyen Duy <dat.nguyenduy@nxp.com>
2022-06-18 18:09:49 +02:00
if(CONFIG_DCLS AND NOT CONFIG_FP_HARDABI)
cmake: gcc: target_arm: Force FP hard ABI for DCLS When Dual-redundant Core Lock-step (DCLS) topology is used, the VFP registers across the two redundant cores must be manually initialised and synchronised, and this requires the `-mfloat-abi=hard` option to be specified. This commit forces the use of FP "hard" ABI on the VFP-equipped cores that are configured in DCLS topology. Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
2020-03-31 03:06:32 +02:00
# If the processor is equipped with VFP and configured in DCLS topology,
# the FP "hard" ABI must be used in order to facilitate the FP register
# initialisation and synchronisation.
set(FORCE_FP_HARDABI TRUE)
endif()
if (CONFIG_FP_HARDABI OR FORCE_FP_HARDABI)
cmake/target_arm: Use NO_SPLIT for TOOLCHAIN_LD_FLAGS The whole set of architecture flags must be specified together as they might not make sense in isolation, e.g. -mfloat-abi=hard requires a -mcpu value that might have an FPU. Use the NO_SPLIT feature to bind all of the linker options together so that the linker can compute the correct linker paths for toolchain-provided libraries like libc and libgcc. Signed-off-by: Keith Packard <keithp@keithp.com>
2022-10-21 00:09:50 +02:00
list(APPEND ARM_C_FLAGS -mfloat-abi=hard)
cmake: gcc: target_arm: Force FP hard ABI for DCLS When Dual-redundant Core Lock-step (DCLS) topology is used, the VFP registers across the two redundant cores must be manually initialised and synchronised, and this requires the `-mfloat-abi=hard` option to be specified. This commit forces the use of FP "hard" ABI on the VFP-equipped cores that are configured in DCLS topology. Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
2020-03-31 03:06:32 +02:00
elseif(CONFIG_FP_SOFTABI)
cmake/target_arm: Use NO_SPLIT for TOOLCHAIN_LD_FLAGS The whole set of architecture flags must be specified together as they might not make sense in isolation, e.g. -mfloat-abi=hard requires a -mcpu value that might have an FPU. Use the NO_SPLIT feature to bind all of the linker options together so that the linker can compute the correct linker paths for toolchain-provided libraries like libc and libgcc. Signed-off-by: Keith Packard <keithp@keithp.com>
2022-10-21 00:09:50 +02:00
list(APPEND ARM_C_FLAGS -mfloat-abi=softfp)
cmake: compiler: introduce target_arm.cmake Pull ARM flags into cmake/compiler/gcc/target.cmake to be reused between gcc and clang. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2019-09-19 02:41:37 +02:00
endif()
endif()
arch: arm: aarch32: Add half-precision floating-point configs This commit adds the half-precision (16-bit) floating-point configurations to the ARM AArch32 architectures. Enabling CONFIG_FP16 has the effect of specifying `-mfp16-format` option (in case of GCC) which allows using the half-precision floating point types such as `__fp16` and `_Float16`. Note that this configuration can be used regardless of whether a hardware FPU is available or supports half-precision operations. When an FP16-capable FPU is not available, the compiler will automatically provide the software emulations. Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
2021-08-18 14:04:45 +02:00
if(CONFIG_FP16)
if (CONFIG_FP16_IEEE)
cmake/target_arm: Use NO_SPLIT for TOOLCHAIN_LD_FLAGS The whole set of architecture flags must be specified together as they might not make sense in isolation, e.g. -mfloat-abi=hard requires a -mcpu value that might have an FPU. Use the NO_SPLIT feature to bind all of the linker options together so that the linker can compute the correct linker paths for toolchain-provided libraries like libc and libgcc. Signed-off-by: Keith Packard <keithp@keithp.com>
2022-10-21 00:09:50 +02:00
list(APPEND ARM_C_FLAGS -mfp16-format=ieee)
arch: arm: aarch32: Add half-precision floating-point configs This commit adds the half-precision (16-bit) floating-point configurations to the ARM AArch32 architectures. Enabling CONFIG_FP16 has the effect of specifying `-mfp16-format` option (in case of GCC) which allows using the half-precision floating point types such as `__fp16` and `_Float16`. Note that this configuration can be used regardless of whether a hardware FPU is available or supports half-precision operations. When an FP16-capable FPU is not available, the compiler will automatically provide the software emulations. Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
2021-08-18 14:04:45 +02:00
elseif(CONFIG_FP16_ALT)
cmake/target_arm: Use NO_SPLIT for TOOLCHAIN_LD_FLAGS The whole set of architecture flags must be specified together as they might not make sense in isolation, e.g. -mfloat-abi=hard requires a -mcpu value that might have an FPU. Use the NO_SPLIT feature to bind all of the linker options together so that the linker can compute the correct linker paths for toolchain-provided libraries like libc and libgcc. Signed-off-by: Keith Packard <keithp@keithp.com>
2022-10-21 00:09:50 +02:00
list(APPEND ARM_C_FLAGS -mfp16-format=alternative)
arch: arm: aarch32: Add half-precision floating-point configs This commit adds the half-precision (16-bit) floating-point configurations to the ARM AArch32 architectures. Enabling CONFIG_FP16 has the effect of specifying `-mfp16-format` option (in case of GCC) which allows using the half-precision floating point types such as `__fp16` and `_Float16`. Note that this configuration can be used regardless of whether a hardware FPU is available or supports half-precision operations. When an FP16-capable FPU is not available, the compiler will automatically provide the software emulations. Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
2021-08-18 14:04:45 +02:00
endif()
endif()
arch: arm: cortex_ar: Use TPIDRURW as a base pointer for TLS Replace the TLS base address pointer from TPIDRURO to TPIDRURW. The difference between them is that TPIDRURO is read-only in user mode but TPIDRURW isn't. So TPIDRURO is much more suitable for store the address of _kernel.CPU[n]. For this reason, this commit replaces the base pointer of the TLS area. Signed-off-by: Huifeng Zhang <Huifeng.Zhang@arm.com>
2023-07-27 10:42:34 +02:00
if(CONFIG_THREAD_LOCAL_STORAGE)
list(APPEND ARM_C_FLAGS -mtp=soft)
endif()
cmake/target_arm: Use NO_SPLIT for TOOLCHAIN_LD_FLAGS The whole set of architecture flags must be specified together as they might not make sense in isolation, e.g. -mfloat-abi=hard requires a -mcpu value that might have an FPU. Use the NO_SPLIT feature to bind all of the linker options together so that the linker can compute the correct linker paths for toolchain-provided libraries like libc and libgcc. Signed-off-by: Keith Packard <keithp@keithp.com>
2022-10-21 00:09:50 +02:00
list(APPEND TOOLCHAIN_C_FLAGS ${ARM_C_FLAGS})
list(APPEND TOOLCHAIN_LD_FLAGS NO_SPLIT ${ARM_C_FLAGS})
llext: move all flags to compiler specific cmake files Minimize the amount of flags that are hardcoded in the llext.cmake module by moving them to the compiler specific cmake files. The llext.cmake module will now use the new LLEXT_REMOVE_FLAGS and LLEXT_APPEND_FLAGS global variables to adjust the set of flags used to compile the llext code. This will make it easier to add support for new architectures and compilers. Signed-off-by: Luca Burelli <l.burelli@arduino.cc>
2024-01-19 13:00:38 +01:00
# Flags not supported by llext linker
# (regexps are supported and match whole word)
set(LLEXT_REMOVE_FLAGS
-fno-pic
-fno-pie
-ffunction-sections
-fdata-sections
-g.*
-Os
)
# Flags to be added to llext code compilation
set(LLEXT_APPEND_FLAGS
-mlong-calls
-mthumb
)
Reference in a new issue Copy permalink