Anonymous
8/20/2025, 3:10:44 PM
No.106323735
>>106323672
>when do you ever have a free-standing, heapless environments? no useful micro controller has so little RAM that you cannot allocate a 4k heap
I was just curious about the support.
After I have moved away from RTOS and went bare metal, I did allocated some heap but quickly realized I am literally never using it for anything. All my buffers and stuff are statically allocated and I have no use of dynamic memory at all. I will still need it later on for some stuff, but for now I was really surprised with how everything just werks on no_std without needing any dynamic allocations. Reading your post I got curious how would C++ perform in such scenario since the stdlib seemed dodgy at places.
Is there any mechanism of disabling or generalizing parts of standard library that depend on OS specific features like heap or mutexes? Or do you just write code until it fails to compile because of missing symbols or something?
>when do you ever have a free-standing, heapless environments? no useful micro controller has so little RAM that you cannot allocate a 4k heap
I was just curious about the support.
After I have moved away from RTOS and went bare metal, I did allocated some heap but quickly realized I am literally never using it for anything. All my buffers and stuff are statically allocated and I have no use of dynamic memory at all. I will still need it later on for some stuff, but for now I was really surprised with how everything just werks on no_std without needing any dynamic allocations. Reading your post I got curious how would C++ perform in such scenario since the stdlib seemed dodgy at places.
Is there any mechanism of disabling or generalizing parts of standard library that depend on OS specific features like heap or mutexes? Or do you just write code until it fails to compile because of missing symbols or something?