RIOT/tests/ssp/Makefile

include ../Makefile.tests_common

USEMODULE += ssp

# This test intentionally crashes the firmware and when using a board with
# stdio via CDC ACM, RIOT can't print anything after the crash.
FEATURES_BLACKLIST += highlevel_stdio

include $(RIOTBASE)/Makefile.include

ifneq (,$(shell $(CC) --help=warnings | grep '\-Wstringop-overflow='))
  CFLAGS += -Wstringop-overflow=0
endif

ifneq (,$(shell $(CC) --help=warnings | grep '\-Warray-bounds='))
  CFLAGS += -Warray-bounds=0
endif
tests: add SSP (stack smashing protector) test application 2016-12-04 20:55:33 +01:00			`include ../Makefile.tests_common`

			`USEMODULE += ssp`

tests: blacklist highlevel_stdio instead of bootloader_% 2020-09-22 14:41:44 +02:00			`# This test intentionally crashes the firmware and when using a board with`
			`# stdio via CDC ACM, RIOT can't print anything after the crash.`
			`FEATURES_BLACKLIST += highlevel_stdio`
tests/ssp: blacklist bootloader_arduino feature 2020-03-11 11:45:42 +01:00
tests: add SSP (stack smashing protector) test application 2016-12-04 20:55:33 +01:00			`include $(RIOTBASE)/Makefile.include`
tests/ssp: warning stringop-overflow has to be disabled Newer gcc versions have an option to enable overflow warnings for string operations. This option is enabled by default. For this test, it is necessary to disable this warning if the compiler supports this option. 2019-11-21 16:02:06 +01:00
			`ifneq (,$(shell $(CC) --help=warnings \| grep '\-Wstringop-overflow='))`
			`CFLAGS += -Wstringop-overflow=0`
			`endif`
tests/ssp: silence array-bounds warning if present This warning is triggered on gcc 10 with riscv and makes the build to fail 2021-02-09 17:10:21 +01:00
			`ifneq (,$(shell $(CC) --help=warnings \| grep '\-Warray-bounds='))`
			`CFLAGS += -Warray-bounds=0`
			`endif`