Gaurav-Aggarwal-AWS

This is something that is hard to implement generically. One way could be to use MPU to catch MSP overflows. You can use a block of memory for main stack...

As Richard explained, we do not have a separate STM32 port. If you want to do it for your application, you can possibly use [traceTASK_SWITCHED_OUT](https://github.com/FreeRTOS/FreeRTOS-Kernel/blob/main/tasks.c#L3030) macro and put a check...

> You would have to define a maximum MSP Stack size. It could be in the linker script. But for this purpose it would have to be in the FreeRTOS...

Thank you for the change and apologies for the delay in getting back on this. If I understand correctly, you are adding support for additional TLS (Thread Local Storage) when...

Thank you for the clarification. We are discussing internally - will get back to you.

This PR generalizes the TLS support in FreeRTOS so that it is no longer newlib specific - https://github.com/FreeRTOS/FreeRTOS-Kernel/pull/540. This should be sufficient to enable TLS support for picolibc? Thanks.

Given that I have merged the other PR, can we close this one?

What do you think about moving this code to the application (i.e. FreeRTOSConfig.h)? This lets the application writer control which memory block is used for TLS - part of task...

> This code relies on internal details of where the macros are used -- they have to reference pxTopOfStack, which is a local variable in prvInitialiseNewTask. To me, this means...

This is more of a feature request for new GIC which does not have memory mapped interface for CPU. Thank you for your post.