RIOT-OS/RIOT
RIOT-OS/RIOT
1
0
Fork 0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00
Code Releases Activity
43befee63c
RIOT/makefiles/arch/riscv.inc.mk

56 lines
2.1 KiB
Makefile
Raw Normal View History

cpu/fe310: add RISC-V cpu FE310 New CPU FE310 from SiFive based on RISC-V architecture build: add makefile for RISC-V builds Makefile for builds using RISC-V tools
2018-04-16 19:03:33 +02:00
# Target architecture for the build.
build system: use riscv-none-elf as triplet Use riscv-none-elf instead of legacy riscv-none-embed as target triplet for RISC-V development. However, if ricsv-none-elf is not present, try riscv64-unknown-elf and riscv-none-embed instead. If the legacy riscv-none-embed is used, a warning is printed.
2020-09-07 22:21:42 +02:00
makefiles/arch/riscv.inc.mk: Detect target triple This improves the target triple detection logic to include all possible target triples of compilers that might be able to generate our binaries.
2020-11-06 09:54:45 +01:00
# The correct triple for 32 bit embedded RISC-V targets is "riscv32-none-elf".
# However, is unknown is used as sys (in place of none), it will also fall back
# to none. Finally, if the GCC RISC-V cross compiler is compiled with full
# multilib support, it can create both 32 bit and 64 bit binaries. Often this is
# indicated with "riscv" being used instead of "riscv32/riscv64", but e.g.
# Ubuntu uses "riscv64-unknown-elf" despite being able to produce both 32 and
# 64 bit binaries. We'll test all possible combinations from the most correct
# triple to the least correct triple all that might be able to produce our
# binaries. Finally, "riscv-none-embed" is also tested for compatibility with
# an previously popular legacy toolchain.
_TRIPLES_TO_TEST := \
riscv32-none-elf \
riscv-none-elf \
riscv32-unknown-elf \
riscv-unknown-elf \
riscv64-none-elf \
riscv64-unknown-elf \
riscv-none-embed
TARGET_ARCH_RISCV ?= \
$(strip \
$(subst -gcc,,\
$(notdir \
$(word 1,\
Revert "Remove `which` from shell invocations"
2021-09-03 11:27:03 +02:00
$(foreach triple,$(_TRIPLES_TO_TEST),$(shell which $(triple)-gcc 2> /dev/null))))))
build system: use riscv-none-elf as triplet Use riscv-none-elf instead of legacy riscv-none-embed as target triplet for RISC-V development. However, if ricsv-none-elf is not present, try riscv64-unknown-elf and riscv-none-embed instead. If the legacy riscv-none-embed is used, a warning is printed.
2020-09-07 22:21:42 +02:00
build system: Overwrite TARGET_ARCH per arch Add `TARGET_ARCH_<ARCH>` for each architecture (e.g. `TARGET_ARCH_CORTEX` for Cortex M) to allow users to overwrite the target triple for a specific arch from ~/.profile or ~/.bashrc (or the like) without overwriting it for all others as well.
2020-09-08 22:28:41 +02:00
TARGET_ARCH ?= $(TARGET_ARCH_RISCV)
cpu/fe310: add RISC-V cpu FE310 New CPU FE310 from SiFive based on RISC-V architecture build: add makefile for RISC-V builds Makefile for builds using RISC-V tools
2018-04-16 19:03:33 +02:00
# define build specific options
fe310: Support the LLVM toolchain (i.e. compilation with clang) This requires -nostartfiles to be only passed to the linker, not the compiler, as it is a linker flag and passing it to the compiler causes a clang warning to be emitted. Additionally, clang does not seem to support `-mcmodel=medlow` and `-msmall-data-limit=8` but these options do not seem strictly necessary to me anyhow thus they are deactivated conditionally when using clang.
2020-10-07 09:37:52 +02:00
CFLAGS_CPU = -march=rv32imac -mabi=ilp32
ifeq ($(TOOLCHAIN),llvm)
# Always use riscv32-none-elf as target triple for clang, as some
# autodetected gcc target triples are incompatible with clang
TARGET_ARCH_LLVM := riscv32-none-elf
else
CFLAGS_CPU += -mcmodel=medlow -msmall-data-limit=8
arch/riscv: use natural malign-data type
2021-02-09 10:45:51 +01:00
ifneq (,$(shell $(TARGET_ARCH)-gcc --help=target | grep '\-malign-data='))
CFLAGS_CPU += -malign-data=natural
endif
fe310: Support the LLVM toolchain (i.e. compilation with clang) This requires -nostartfiles to be only passed to the linker, not the compiler, as it is a linker flag and passing it to the compiler causes a clang warning to be emitted. Additionally, clang does not seem to support `-mcmodel=medlow` and `-msmall-data-limit=8` but these options do not seem strictly necessary to me anyhow thus they are deactivated conditionally when using clang.
2020-10-07 09:37:52 +02:00
endif
CFLAGS_LINK = -ffunction-sections -fdata-sections
cpu/fe310: change default optimization to "-Os" Also moves the option to CFLAGS_OPT.
2019-10-21 11:27:21 +02:00
CFLAGS_DBG ?= -g3
CFLAGS_OPT ?= -Os
cpu/fe310: add RISC-V cpu FE310 New CPU FE310 from SiFive based on RISC-V architecture build: add makefile for RISC-V builds Makefile for builds using RISC-V tools
2018-04-16 19:03:33 +02:00
riscv_common: Refactor common fe310 code to riscv_common
2020-09-09 21:37:15 +02:00
LINKFLAGS += -L$(RIOTCPU)/$(CPU)/ldscripts -L$(RIOTCPU)/riscv_common/ldscripts
make/riscv: remove use of export for LINKFLAGS
2020-01-02 09:51:20 +01:00
LINKER_SCRIPT ?= $(CPU_MODEL).ld
LINKFLAGS += -T$(LINKER_SCRIPT)
cpu/fe310: add RISC-V cpu FE310 New CPU FE310 from SiFive based on RISC-V architecture build: add makefile for RISC-V builds Makefile for builds using RISC-V tools
2018-04-16 19:03:33 +02:00
makefiles: do not locally export compilation variables These are already exported by `makefiles/vars.inc.mk`. It is a prerequisite to allow handling compilation without global exports.
2019-08-27 16:06:41 +02:00
CFLAGS += $(CFLAGS_CPU) $(CFLAGS_DBG) $(CFLAGS_OPT) $(CFLAGS_LINK)
ASFLAGS += $(CFLAGS_CPU) $(CFLAGS_DBG)
cpu/fe310: add RISC-V cpu FE310 New CPU FE310 from SiFive based on RISC-V architecture build: add makefile for RISC-V builds Makefile for builds using RISC-V tools
2018-04-16 19:03:33 +02:00
# export linker flags
fe310: Support the LLVM toolchain (i.e. compilation with clang) This requires -nostartfiles to be only passed to the linker, not the compiler, as it is a linker flag and passing it to the compiler causes a clang warning to be emitted. Additionally, clang does not seem to support `-mcmodel=medlow` and `-msmall-data-limit=8` but these options do not seem strictly necessary to me anyhow thus they are deactivated conditionally when using clang.
2020-10-07 09:37:52 +02:00
LINKFLAGS += $(CFLAGS_CPU) $(CFLAGS_LINK) $(CFLAGS_DBG) $(CFLAGS_OPT) -nostartfiles -Wl,--gc-sections -static -lgcc
Copy Permalink