l4re-base-25.08.0

This commit is contained in:
2025-09-12 15:55:45 +02:00
commit d959eaab98
37938 changed files with 9382688 additions and 0 deletions

View File

@@ -0,0 +1,29 @@
# vim:se ft=make:
CROSS_COMPILE_riscv = riscv64-linux-gnu-
ASFLAGS_riscv = -Wa,--noexecstack
ELF_BINARY_TYPE_riscv = elf$(BITS)
LD_EMULATION_CHOICE_riscv = $(ELF_BINARY_TYPE_riscv)lriscv
OFORMAT_riscv = $(ELF_BINARY_TYPE_riscv)-littleriscv
BFD_ARCH_riscv = littleriscv
L4_KIP_ADDR_riscv ?= 0x7fff0000
L4_STACK_ADDR_riscv ?= 0x70000000
# Since version 2.38, binutils by default targets the ISA specification version
# 20191213, where the CSR instructions and the FENCE.I instruction have been
# moved from the I extension into separate extensions: Zicsr and Zifencei
RISCV_ZICSR_ZIFENCEI_riscv_f = $(if $(call checkcc,-march=$(CPU)_zicsr_zifencei \
-mabi=$(CPU_ABI) \
-mcmodel=medany),_zicsr_zifencei)
CARCHFLAGS_riscv += -march=$(CPU)$(RISCV_ZICSR_ZIFENCEI_riscv) \
-mabi=$(CPU_ABI) -mcmodel=medany
LDFLAGS_riscv += -z noexecstack
SYSTEMS_ABI += riscv-l4f
SYSTEMS_PLAIN += riscv-plain
# As of now (gcc-12) there is no option to prevent the compiler from generating
# FPU instructions. So we just have to assume that the compiler does not do it,
# until it introduces a flag able to prevent it.
GCCNOFPU_riscv_f =
QEMU_ARCH_MAP_riscv = qemu-system-riscv$(BITS)