https://devzone.nordicsemi.com/f/nordic-q-a/7193/am-i-allowed-to-eat-up-a-little-bit-of-ram-space-from-s110Hello, I am developing on top of S110, for nrf51822_xxaa, building with GCC. And as my code is growing, even after mapping inspection, gcc optimizations, stripping, heap reduction and using nano lib, I am still reaching the infamous link error : en-USTelligent Community 13Thu, 21 May 2015 19:17:45 GMThttps://devzone.nordicsemi.com/thread/25428?ContentTypeID=1Thu, 21 May 2015 19:17:45 GMT137ad170-7792-4731-bb38-c0d22fbe4515:88274968-e6da-444c-93fa-fe225b3cb6c4John<p>Just to expand on part of Nick&#39;s answer: If you are not using dynamic memory allocation such as malloc, you can set the heap to zero and get back 2K of RAM.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/25427?ContentTypeID=1Thu, 21 May 2015 18:49:03 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e72bf758-7c3a-4d28-8c3f-e9bb1b904e67Jean-Louis Bonnaff&#233;<p>reducing the stack size in the gcc_startup_nrf51.s did the trick - Thanks a ton, Nick !</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/25426?ContentTypeID=1Thu, 21 May 2015 18:29:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:6f5adfc0-d318-4f92-bfc4-1b455d9d240aNick Pelis<p>Depending on your requirements, you may be able to shrink the size of the heap and stack. Check out arm_startup_nrf51.s.</p> <p>Also keep in mind indirect function calls (e.g., C++ code, structs of function pointers) are complicated for the compiler to implement on the Cortex-M0 architecture, resulting in more assembly instructions and larger code. Same applies for indirect memory reads/writes (e.g. pointers to arrays, arrays of pointers, double-pointers, etc.).</p><div style="clear:both;"></div>