[riot-notifications] [RIOT-OS/RIOT] sys/Makefile.include: check for newlib_nano instead of USE_NANO_SPECS (#11883)

Gaëtan Harter notifications at github.com
Mon Jul 22 18:39:22 CEST 2019

I have a weird thing. I manage to make `printf_float` unittest work by moving the stack from `.bss` to `.data`. (not sure if the syntax is really initializing everything but it makes it work).

<details><summary><code>BOARD=msba2 make --no-print-directory -C tests/unittests/ clean tests-printf_float  flash-only test</code></summary>

/srv/ilab-builds/boards/RIOT/dist/tools/pyterm/pyterm -tg -p "/dev/riot/ttyMSBA2"
Twisted not available, please install it if you want to use pyterm's JSON capabilities
2019-07-22 18:31:56,087 - INFO # Connect to serial port /dev/riot/ttyMSBA2
Welcome to pyterm!
Type '/exit' to exit.
2019-07-22 18:31:57,094 - INFO # main(): This is RIOT! (Version: 2019.10-devel-106-g2d5ed-pr/newib/remove_use_nano_specs_variable)
2019-07-22 18:31:57,095 - INFO # .
2019-07-22 18:31:57,095 - INFO # OK (1 tests)

I also checked when using `printf`.

``` diff
diff --git a/core/kernel_init.c b/core/kernel_init.c
index 1b153b38a..bb61c5dd9 100644
--- a/core/kernel_init.c
+++ b/core/kernel_init.c
@@ -74,7 +74,7 @@ static void *idle_thread(void *arg)
 const char *main_name = "main";
 const char *idle_name = "idle";

-static char main_stack[THREAD_STACKSIZE_MAIN];
+static char main_stack[THREAD_STACKSIZE_MAIN] = {0xff};
 static char idle_stack[THREAD_STACKSIZE_IDLE];

 void kernel_init(void)

Smells like `ldscript` issues.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190722/1bbf5c8d/attachment.htm>

More information about the notifications mailing list