OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/cmake/compiler/gcc/target_x86.cmake

24 lines
774 B
CMake
Raw Normal View History

cmake: need to specify m32/m64 for x86_64 toolchain Since x86_64-zephyr-elf is a multi-lib toolchain, m32/m64 need to be specified for the compiler to return the correct library path when queried (e.g. --print-libgcc-file-name). This affects the compile check done by CMake. Without these flags, the compiler returns incorrect toolchain path (e.g. requiring 64-bit libraries but returning 32-bit library path). This also affects compiler flag checks for "-lstdc++". Incorrect library path results in error when checking for "-lstdc++", and this flag will not be used for the build. This results in undefined references when compiling C++ code. This creates target_x86.cmake to add the necessary flags for CMake to use. The target_x86_64.cmake is also created to mirror the same change. Also removing the -m32 flags for host-gcc since we are not building x86 targets with the host-gcc compiler. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2019-10-08 16:14:02 +08:00
# SPDX-License-Identifier: Apache-2.0
if(CONFIG_X86_64)
string(PREPEND CMAKE_ASM_FLAGS "-m64 ")
string(PREPEND CMAKE_C_FLAGS "-m64 ")
string(PREPEND CMAKE_CXX_FLAGS "-m64 ")
else()
string(PREPEND CMAKE_ASM_FLAGS "-m32 ")
string(PREPEND CMAKE_C_FLAGS "-m32 ")
string(PREPEND CMAKE_CXX_FLAGS "-m32 ")
x86: enable soft float support for Zephyr SDK This adds the correct compiler and linker flags to support software floating point operations. The flags need to be added to TOOLCHAIN_*_FLAGS for GCC to find the correct library (when calling GCC with --print-libgcc-file-name). Note that software floating point needs to be turned on for Newlib. This is due to Newlib having floating point numbers in its various printf() functions which results in floating point instructions being emitted from toolchain. These instructions are placed very early in the functions which results in them being executed even though the format string contains no floating point conversions. Without using CONFIG_FPU to enable hardware floating point support, any calls to printf() like functions will result in exceptions complaining FPU is not available. Although forcing CONFIG_FPU=y with newlib is an option, and because the OS doesn't know which threads would call these printf() functions, Zephyr has to assume all threads are using FPU and thus incurring performance penalty as every context switching now needs to save FPU registers. A compromise here is to use soft float instead. Newlib with soft float enabled does not have floating point instructions and yet can still support its printf() like functions. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2020-12-11 05:08:33 +08:00
if(CONFIG_X86_FP_USE_SOFT_FLOAT)
list(APPEND TOOLCHAIN_C_FLAGS -msoft-float)
list(APPEND TOOLCHAIN_LD_FLAGS -msoft-float)
endif()
cmake: need to specify m32/m64 for x86_64 toolchain Since x86_64-zephyr-elf is a multi-lib toolchain, m32/m64 need to be specified for the compiler to return the correct library path when queried (e.g. --print-libgcc-file-name). This affects the compile check done by CMake. Without these flags, the compiler returns incorrect toolchain path (e.g. requiring 64-bit libraries but returning 32-bit library path). This also affects compiler flag checks for "-lstdc++". Incorrect library path results in error when checking for "-lstdc++", and this flag will not be used for the build. This results in undefined references when compiling C++ code. This creates target_x86.cmake to add the necessary flags for CMake to use. The target_x86_64.cmake is also created to mirror the same change. Also removing the -m32 flags for host-gcc since we are not building x86 targets with the host-gcc compiler. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2019-10-08 16:14:02 +08:00
endif()
cmake: add --divide to GNU assembler options for x86 GNU Assembler, by default on non-Linux targets, treats slashes as start of comments on i386. (https://sourceware.org/binutils/docs-2.33.1/as/i386_002dChars.html#i386_002dChars) In order to use division, `--divide` needs to be passed to the assembler. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2019-10-30 03:58:07 +08:00
# GNU Assembler, by default on non-Linux targets, treats slashes as
# start of comments on i386.
# (https://sourceware.org/binutils/docs-2.33.1/as/i386_002dChars.html#i386_002dChars)
# In order to use division, `--divide` needs to be passed to
# the assembler.
list(APPEND TOOLCHAIN_C_FLAGS -Wa,--divide)