Why do cflags have heap and stack size

[Jimmie Johansson]

I have inherited a project where the Makefile sets __HEAP_SIZE and __STACK_SIZE for both CFLAGS and ASMFLAGS:

CFLAGS += -D__STACK_SIZE=2048
CFLAGS += -D__HEAP_SIZE=0
ASMFLAGS += -D__STACK_SIZE=2048
ASMFLAGS += -D__HEAP_SIZE=0

Looking at samle Makefiles from the SDK I see the same (but only for __HEAP_SIZE). But the only place I can find that use __HEAP_SIZE and __STACK_SIZE is in the .s files. Does anyone know a case where the __STACK_SIZE and __HEAP_SIZE in CFLAGS is used?

[endnode]

These variables are used in xxx_startup_yyy.s files.

[Jimmie Johansson]

Yes, but all .s files are built with the ASMFLAGS, why are the variables included in CFLAGS?

[endnode]

Good point. The only place I see it in SDK v14 is nRF5_SDK_14.0.0_3bcc1f7\external\freertos\source\include\task.h, that should not justify its presence in CFLAGS;)