SDK GCC linker script placing constants in RAM?https://devzone.nordicsemi.com/f/nordic-q-a/69771/sdk-gcc-linker-script-placing-constants-in-ramPerusing the GCC linker script supplied as part of SDK v16, I noticed that the .data section is specified as follows: .data : AT (__etext) { __data_start__ = .; *(vtable) *(.data*) . = ALIGN(4); /* preinit data */ PROVIDE_HIDDEN (__preinit_array_starten-USTelligent Community 13Tue, 22 Dec 2020 09:32:41 GMTRE: SDK GCC linker script placing constants in RAM?https://devzone.nordicsemi.com/thread/286241?ContentTypeID=1Tue, 22 Dec 2020 09:32:41 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b1b32041-21e1-4749-94a1-663a9e39efa4Einar Thorsrud<p>Hi,</p> <p>This has been like this for a long time. I suspect this is a consequence of Nordic not using much C++, and therefore never having been in a position where we needed to optimize this. I have asked the team responsible for this to comment, but I do not expect to have more until beginning of January.</p> <p>Update: I got feedback from the team responsible for the MDK and according to them there is no strong rationale for placing the vtable in RAM. You should consider it a default that can be changed without any side effects if that fits your application better (typically if it is RAM constrained).</p><div style="clear:both;"></div>