RIOT/cpu/fe310/Makefile.features

FEATURES_PROVIDED += arch_32bit
FEATURES_PROVIDED += arch_riscv
FEATURES_PROVIDED += cpp
FEATURES_PROVIDED += libstdcpp
FEATURES_PROVIDED += newlib
FEATURES_PROVIDED += periph_cpuid
FEATURES_PROVIDED += periph_gpio periph_gpio_irq
FEATURES_PROVIDED += periph_plic
FEATURES_PROVIDED += periph_pm
FEATURES_PROVIDED += periph_wdt
FEATURES_PROVIDED += ssp

# RISC-V toolchain on CI does not work properly with picolibc yet
ifeq (,$(RIOT_CI_BUILD))
  FEATURES_PROVIDED += picolibc
endif
cpu: add missing arch features to fe310 Adds arch_32bit and arch_riscv to cpu/fe310 to allow for feature requirements and blacklisting. 2019-10-14 17:40:23 +02:00			`FEATURES_PROVIDED += arch_32bit`
			`FEATURES_PROVIDED += arch_riscv`
cpu/fe310: add cpp feature 2019-12-05 16:17:02 +01:00			`FEATURES_PROVIDED += cpp`
build system: Add libstdcpp feature and doc - Add libstdcpp feature to indicate a platform is providing a libstdc++ implementation ready for use - The existing cpp feature now only indicates a working C++ toolchain without libstdc++. (E.g. still useful for the Arduino compatibility layer.) - Added libstdcpp as required feature were needed - Added some documentation on C++ on RIOT 2020-07-12 22:53:30 +02:00			`FEATURES_PROVIDED += libstdcpp`
treewide: model newlib as a FEATURE 2021-01-26 14:55:40 +01:00			`FEATURES_PROVIDED += newlib`
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			`FEATURES_PROVIDED += periph_cpuid`
cpu/fe310: provide gpio feature at cpu level 2019-12-05 14:05:17 +01:00			`FEATURES_PROVIDED += periph_gpio periph_gpio_irq`
fe310: Add PLIC peripheral driver 2020-08-28 20:31:31 +02:00			`FEATURES_PROVIDED += periph_plic`
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			`FEATURES_PROVIDED += periph_pm`
cpu/fe310: implement driver for watchdog 2019-11-07 14:12:07 +01:00			`FEATURES_PROVIDED += periph_wdt`
Add CPU feature for stack smash protections 2020-01-22 15:26:19 +01:00			`FEATURES_PROVIDED += ssp`
cpu/fe310: blacklist picolibc on CI The RISC-V toolchain in riotdocker has issues with picolibc and will still include newlib headers. This leads to conflicts like ``` In file included from [01m[Knanostubs.c:22[m[K: [01m[K/usr/local/picolibc/riscv-none-embed/include/stdio.h:270:23:[m[K [01;31m[Kerror: [m[Kconflicting types for '[01m[K__FILE[m[K' typedef struct __file [01;31m[K__FILE[m[K; [01;31m[K^~~~~~[m[K In file included from [01m[K/opt/gnu-mcu-eclipse/riscv-none-gcc/8.2.0-2.2-20190521-0004/riscv-none-embed/include/reent.h:93[m[K, from [01m[Knanostubs.c:20[m[K: [01m[K/opt/gnu-mcu-eclipse/riscv-none-gcc/8.2.0-2.2-20190521-0004/riscv-none-embed/include/sys/reent.h:287:26:[m[K [01;36m[Knote: [m[Kprevious declaration of '[01m[K__FILE[m[K' was here typedef struct __sFILE [01;36m[K__FILE[m[K; [01;36m[K^~~~~~[m[K ``` The problem does not occur when installing both the toolchain and picolibc directly from the Debian / Ubuntu repositories, but CI uses an older Ubuntu version that does not have those packages yet, so it builds them manually. Blacklist RISC-V until CI has been updated. 2020-10-14 11:08:36 +02:00
			`# RISC-V toolchain on CI does not work properly with picolibc yet`
			`ifeq (,$(RIOT_CI_BUILD))`
			`FEATURES_PROVIDED += picolibc`
			`endif`