RTEMS | Multiple tests do not consider the Thread Local Storage size (#5498)

[Matteo Concas (@matteo.concas)]

Matteo Concas created an issue: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5498



## Summary
With more recent Newlib version, some objects (like `errno`) have been moved to Thread Local Storage

The following tests are affected (I do not know if it is the full extent):
* flashdev01
* sp01
* ts-fatal-extension
* tc-task-performance
* tr-fatal-idle-thread-stack-too-small
* ts-validation-acfg-0
* ts-validation-acfg-1
* ts-validation-1.exe
* ts-validation-one-cpu-1.exe
* spstkalloc02.exe

Some tests like sptls01.exe and sptls03.exe also require specific TLS sizes which might not be compatible with all architectures (32bit vs 64bit) or all BSPs (especially GRLIB ones) where C library methods are used during BSP initialization.

## Root causes

There are two main root causes I could see:
* The test fail during initialization because they are configured with `CONFIGURE_INIT_TASK_STACK_SIZE` or `CONFIGURE_IDLE_TASK_STORAGE_SIZE` set to `RTEMS_MINIMUM_STACK_SIZE` which is only valid if the TLS size is 0.
* The test fail during testing because a task config has `maximum_thread_local_storage_size = 0` which is only valid if the TLS size is 0. 


<!-- Pre-set options
- milestone
-->

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5498
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260223/8707c790/attachment.htm>