>>106323895
>the compiler i use at work supports multiple different C++ libraries such as embedded, extended embedded, dinkum
>I think the ETL
Oh I see. So libraries typically need extra support from compiler?
In Rust, even when using esp tool chain, you are expected to have any no_std library working out of the box.
>anyway, i forgot to mention in my previous post that the borrow checker, while probably useful, is quite useless when you have two separate binaries on separate CPU cores that share memory/hardware
>but then you need to be able to tell the OS why you are blocking to allow good scheduling
What do you mean? I just spawn async executor on each core and have stuff working in parallel. I use mutexes(implemented using critical sections) and channels to communicate with each other. Tasks pass around static references and singletons representing access to specific buffer/peripheral and things just work. Drivers set up interrupts and use wakers to resume appropriate tasks even across cores, so CPU can sleep when waiting for IO/timers.
Correct me if I'm wrong, but isn't this the right choice?
Here is how are the CPUs performing under heavy load with explicit yields in the drawing tasks. But if it's not doing anything, the CPU is sleeping nearly all the time.