RTEMS | BSS Size Incorrectly Reported (#5191)

Thu Feb 26 08:03:03 UTC 2026

Abdullah Wasiq commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5191#note_143521

At first I thought maybe using different flags for the affected memory regions could be an option. However, it seems that right now there isn't another way to represent reserved memory behaviour for something like `.work` except marking flags for alloc & nobits. This means reserved memory is the same as an entire block of zero bits in the eyes of _size_ because it cannot distinguish from zero-initialized data and reserved memory. 

Maybe we could remove the affected regions entirely as ELF sections. Instead replacing them with linker symbols. However this is reliant on the fact that nothing depends on the regions in question, and I also feel like this is risky.

Another idea could be to write some sort of wrapper for the size util that parses the memory based off of the section names. the only issue here is that names can change per linker script, that and writing a tool for this issue may or may not be overkill.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5191#note_143521
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/20260226/4f59a582/attachment-0001.htm>