RTEMS | cpukit/confdefs: Add CAN stack resource calculation (!1097)

[MITHILESH MATTAPALLI (@mithileshm)]

MITHILESH MATTAPALLI created a merge request: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1097

Project:Branches: mithileshm/rtems:fix-can-stack-memory to rtems/rtos/rtems:main
Author:   MITHILESH MATTAPALLI



## Summary

cpukit/confdefs: Add CAN stack resource calculation

The CAN/CAN FD stack requires a worker task per configured queue. Empirical profiling confirms the CAN worker task utilizes \~404 bytes of stack space on 32-bit architectures.

This patch introduces CONFIGURE_MAXIMUM_CAN_QUEUES to dynamically inject the required CAN worker tasks into the master \_CONFIGURE_TASKS pool. Because the 404-byte usage falls below RTEMS_MINIMUM_STACK_SIZE, provisioning them as standard system tasks automatically guarantees sufficient stack space overhead.

Closes #5193

## Generative AI

* **Prompt used:** Various diagnostic queries regarding QEMU memory starvation errors and RTEMS `confdefs` macro behavior.
* **Which AI model was used:** Gemini 3.1 pro
* **How AI was used for the contribution:** Diagnostic assistance and conceptual understanding. I used the AI as a search/learning tool to help analyze QEMU terminal output during testing and to clarify the architectural flow of RTEMS task provisioning within the `confdefs` system. The actual macro logic, code implementation, and validation were written and executed entirely on my own.
* **Copyright Statement:** I have not used a product that claims copyright over its output, and I have legitimate access to this tool.

<!--Default settings, if it is a dropdown it will set after submission-->

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1097
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/20260302/4ce0b335/attachment-0001.htm>