• Locked Locked
  • Replies 3 replies
  • Subscribers 119 subscribers
  • Views 5129 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Looking for a way to not place any static data in BSS section

Adam Openshaw
Note: This was originally posted on 2nd October 2012 at http://forums.arm.com

The ARM compiler is very strict (and formidable) at placing zero initialized or uninitialized static data > 8 bytes into the BSS section to save space in the image.  I have a use case where I do not want ANY static data in BSS.  I want all of it to go into RO/RW-DATA sections only. 

I've scoured the web looking for something similar or equivalent to the GNU C compiler's -fno-zero-initialized-in-bss option for RVCT, but cannot find anything.  I'm compiling with DS-5. 

Does anyone know if there is a way to compile without placing any static data into the BSS section?  Placing static data into a BSS section is an optimization, and it's only natural that you should be able to disable it.

Thanks,
Meiyo
Parents
  • Note: This was originally posted on 2nd October 2012 at http://forums.arm.com

    Hi, I don't know how to do it in DS-5, but in Keil, you have something called the scatter file where you can use linker commands to specifically place data in your desired memory regions. There's is no special (button-like) options to disable .bss sections.  Check if there's something similar in DS-5 but I think it should be because ARM is the developer of both.

    Good luck
Reply
  • Note: This was originally posted on 2nd October 2012 at http://forums.arm.com

    Hi, I don't know how to do it in DS-5, but in Keil, you have something called the scatter file where you can use linker commands to specifically place data in your desired memory regions. There's is no special (button-like) options to disable .bss sections.  Check if there's something similar in DS-5 but I think it should be because ARM is the developer of both.

    Good luck
Children
No data