News for hackers. Stuff that matters.
Re:Practical Guide to Bare Metal C++ by xyzzy_plugh on Friday June 02, 2017 @03:44PM (#14472777)
But the compiler doesn't optimize out the constructor, right? It can't.

In an RTOS of all places, that seems awfully expensive. One generally avoids wasted resources in embedded -- the trade-off is it requires more care during development.

I've never seen RAII work well in an embedded system. Not being able to handle exceptions or errors during destruction ruins everything.

Re:Practical Guide to Bare Metal C++ by monocasa on Friday June 02, 2017 @04:12PM (#14472940)
> But the compiler doesn't optimize out the constructor, right? It can't.

> In an RTOS of all places, that seems awfully expensive. One generally avoids wasted resources in embedded -- the trade-off is it requires more care during development.

The compiler has no issues "optimizing out" the constructor in my experience. The asm looks just like the equivalent C in all of the cases I've seen.

> I've never seen RAII work well in an embedded system. Not being able to handle exceptions or errors during destruction ruins everything.

I mean, we disallow exceptions anyway. And we use RAII for objects where there isn't a weird failure case to be handled like my example of thread priority guards.

Re:Practical Guide to Bare Metal C++ by fdsfsafasfdas on Friday June 02, 2017 @05:04PM (#14473304)
Disabling exceptions has solved this. There are no need for exceptions in the kernel, and the cost is high.
Re:Practical Guide to Bare Metal C++ by concede_pluto on Friday June 02, 2017 @05:48PM (#14473563)
Isn't table-driven stack unwinding cheaper than having a bunch of functions each check an error code and return to their caller?
Re:Practical Guide to Bare Metal C++ by monocasa on Friday June 02, 2017 @06:03PM (#14473640)
The practicalities of bare metal programming means that a lot of the time an individual work item has to jump contexts (ie. stacks and register sets) in a way that doesn't map cleanly to C++ style exceptions.