11 ms·
Practical Guide to Bare Metal C++
- vvanders 10y agoNice to see some concrete examples of where you don't want exceptions, rtti or dynamic memory. Quite a few developers believe that if you don't have these features you aren't writing "real C++" but it's common practice in quite a few industries where size/performance is critical.
- kartD 10y agoVery true, I'd wager that a significant portion (20-30%) of all of the existing C/C++ codebase fits this description.
- vonmoltke 10y agoI think that attitude deserves some mention in the section discussing why C++ doesn't get used more often. If you listen to the faction who denigrates anything that looks like "C with classes" then C++ is fundamentally incompatible with bare-metal programming.
- pjmlp 10y agoMostly because the "C with classes" crowd tend to be C developers dragged into using a C++ compiler. Personally I like to turn everything on, but I also understand there are use-cases where it isn't possible. My first C++ compiler was Turbo C++ 1.0 for MS-DOS, so I also used this kind of bare metal programming back in the day. What I don't like is "C with classes" which throws away all the safety mechanisms that C++ offers over C, to the point the code could be compiled with a C compiler. However the advices presented in the "Practical Guide to Bare Metal C++" look quite good.
- evincarofautumn 10y agoThere’s something to be said for only using those features of C++ that you really need, if not because the platform demands it, then at least because it goes easier on the language-lawyering part of the brain. I for one am perfectly happy with “C with destructors and templates”. The usual criticism of “C with classes” is levelled at a specific kind of code that’s neither particularly good C++ nor particularly good C. But not all “C with classes” is necessarily that way.
- fsloth 10y ago"If you listen to..." No-one should need to listen to a bunch of fanatics. Different problems are have different constraints. Some problems are easier to solve using a different formalism than some other. People try to sound like Herb Sutter or Stroustrup when peddling their "best practice" advice after looking at a few lines of code and deciding it's not to their liking. Sutter and Stroustrup usually have a grasp of the higher level context, while random best practice commisars in the web, seldom dont. Since C++ contains so many footguns the charitable explanation is that they grasp to the only way of coding they can hold in their head. Damn the establishment! C++ offers a refreshing multiplicty of styles of implementation. ML style for data transforms, lispish dynamic lists for parsers, vanilla object style for some problem domains, relational style with structs of indices for others. Note: solutions of these styles can be wrapped in a nice cplusplushy interface but if one starts to solve the problem from the point of view of designing the class hierarchy rather than looking at the data and transforms required often leads to a technically inferior dessign (by which I mean - my designs became much better after I understood to focus on the latter and not the former). One needs to be strict, yes, but the strictness needs to be on a closer-core-cs-concepts level and not on the class design level. Just wrote a parser in lisp style C++ and loved it (and yes, there were enough constraints to limit C++ as the only language).
- vardump 10y agoYou seem to be talking about usual C++ programming, not bare metal case. Bare metal means no OS, no runtime, no nothing.
- pjmlp 10y agoRuntime is always there, even if it is a thin library to talk to IO pins, or whatever board you happen to plug in.
- vardump 10y ago> thin library to talk to IO pins That might be a bit bad example, because IO pin control is usually compiled to just one or at most a few machine instructions. IO pin control for those is often a macro or intrinsic, not really a library. Sometimes there's no runtime, other than what you implement. That's true bare metal.
- maxxxxx 10y agoIn my mind "real C++" doesn't use RTTI much but relies more on the compiler to figure out things. This and exceptions are things I generally try to avoid as much as possible. I am big fan of templates though.
- fish2000 10y agoYes, there is a Zen state of C++ programming wherein you, the programmer, surrender to the wisdom of the compiler, and in doing so are liberated from caring about the minutiae of the type system, to be carried forth, skyward, on the twin winds of inference and overload resolution. I do enjoy that. RTTI is nothing like this – it’s a red herring, neither elegant nor powerful… at best it’s a misnomer (it’s more like RTT total lack of I, amirite) and at worst a distraction. I dislike exceptions too, but in a difference-of-opinion way where I can be like “OK, that otherwise legible and reasonable code uses exceptions, unlike mine” and it doesn’t make me grimace like I involuntarily do for RTTI… I’d love to be mistaken tho, anyone with an inspiring counterexample, do share.
- jandrewrogers 10y agoMaybe my experience is atypical but RTTI and exceptions are features of C++ that I never see used in real-world C++ almost regardless of the application. When I have seen them used, it is by people new to C++ that haven't fully figured out the common development idioms of the language yet.
- jlarocco 10y agoI've never seen RTTI use in production code. Even with modern C++, RTTI almost always adds too much runtime overhead and negative performance impacts. Most importantly, it's usually a sign of bad design. My experience with exceptions is different, though, and I see them used quite a bit. It depends a lot on the age of the code base and the group working on it. Old code is less likely to use them, and developers with a heavy C background, or a lot of pre-C++98 experience are less like to use them. Except for maybe some tiny embedded systems (like microcontrollers), the overhead of exceptions isn't that bad any more.
- vvanders 10y agoMy experience has been no rtti and no exceptions. Quite a few compilers generate rtti if you use exceptions. Generally I haven't found any error handling solution where exceptions provided superior semantics. The lack of checking means that you can catch more bugs with enum error codes + switch and Wall.
- fauigerzigerk 10y agoThe strange thing about exceptions in C++ is that they make ubiquitous use of RAII a necessity, but at the same time they must not be thrown in destructors. And then C++ exceptions don't come with a stack trace that makes quick and dirty exceptions based code so convenient in Java or C#. I was never a principled opponent of exceptions, but I find myself removing them from more and more code the more thoroughly I think about all the possible error states of code that should really be robust.
- tibbetts 10y ago
- toby 10y agoThe Google C++ style [1] guide bans exceptions entirely and strongly advises against RTTI. [1] https://google.github.io/styleguide/cppguide.html https://google.github.io/styleguide/cppguide.html
- nomel 10y agoThis link is constantly misused. Their reason is having to support legacy code that can't handle exceptions. That's it. From that link: "However, for existing code, the introduction of exceptions has implications on all dependent code. If exceptions can be propagated beyond a new project, it also becomes problematic to integrate the new project into existing exception-free code. Because most existing C++ code at Google is not prepared to deal with exceptions, it is comparatively difficult to adopt new code that generates exceptions." Would the use exceptions if they could do it again?
- vvanders 10y agoLLVM [1] has very similar restrictions for different reasons. [1] http://llvm.org/docs/CodingStandards.html#do-not-use-rtti-or-exceptions http://llvm.org/docs/CodingStandards.html#do-not-use-rtti-or...
- amaks 10y agoNo. The reason they don't use exceptions is because they lead to unreliable code that is difficult to maintain. There are other ways to indicate error situations such as returning error result that caller must handle.
- maxlybbert 10y agoFrom the Google style guide (section on exceptions): "On their face, the benefits of using exceptions outweigh the costs, especially in new projects. However, for existing code, the introduction of exceptions has implications on all dependent code. If exceptions can be propagated beyond a new project, it also becomes problematic to integrate the new project into existing exception-free code. Because most existing C++ code at Google is not prepared to deal with exceptions, it is comparatively difficult to adopt new code that generates exceptions. "Given that Google's existing code is not exception-tolerant, the costs of using exceptions are somewhat greater than the costs in a new project. The conversion process would be slow and error-prone. We don't believe that the available alternatives to exceptions, such as error codes and assertions, introduce a significant burden. "Our advice against using exceptions is not predicated on philosophical or moral grounds, but practical ones. ... Things would probably be different if we had to do it all over again from scratch."
- PopsiclePete 10y agoHonest question: At some point, why even bother with C++? The streams library is a mess - don't use it. Exceptions are too slow - don't use 'em. Can't have exceptions, can't have RAII, MI is bad in 99% of cases - avoid. At some point, you're left with "C with classes", maybe with some templates sprinkled here and there, and nice map/list/string implementations. Ok fine. So is this still C++? And if it is, and if it's exactly what you need, and C is still not good enough, maybe there's a use-case for either a new language, call is --C++, or some kind of "C++ without the bad stuff" accepted standard to drive the entire eco-system forward with well-defined features, boundaries, libraries, tools, all that good stuff?
- kchoudhu 10y agoThe more I mess around with Rust, the more it seems to fit the bill as the new --C++.
- pandaman 10y agoI don't feel like I have to use every single feature of a language. I prefer C++ over C for: namespaces, overloads, encapsulation and user defined types. E.g. I'd rather write simple expressions for vector math than a bunch of function calls. I'd rather have the compiler enforce the type invariants than do runtime checks everywhere. I'd rather have my ids without prefixes to evade name conflicts etc. etc. As for your proposal - why? I can already disable exceptions and RTTI with compiler switches. And is it really a sane idea to spin off a new language if you don't like some library?
- Taniwha 10y agoHe's talking about real time code here and completely missing one of the main reasons why you have to use great care using C++, and even parts of the C libraries ... all those hidden mutexes in new/malloc and other parts of the standard libraries (stdio too) I'm sure we all know what happens when your ISR quietly does a new while some other part of your code is holding one of the locks deep in malloc. But far more important is avoiding priority inversions when a low priority thread is holding a lock in a library somewhere, they result in high priority threads missing real-time deadlines - the sort of heisenbugs that are pretty impossible to find .... and are best to avoid by design.
- webkike 10y agoWell, if you're programming bare metal you shouldn't be using any library's allocation routines but your own. Because, remember the cardinal rule: no mutices in ISRs!
- Taniwha 10y agoI was kind of pointing out that people know that mutexes in ISRs are a bad idea, but don't know as much about the other dragons that live in the same swamp ... they may also simply not be aware of what's inside their libraries (which ones use mutexes? 'man printf' doesn't warn me) my point is that there are hidden mutexes in libraries that people often don't know about - his example of replacing new() with malloc() doesn't solve the problem, instead you need to be able to code your C++ without new, or at least the real-time bits of it (and that includes using stuff like strings and their libraries that do new() behind your back, or even printf which can run foul of the stdio hidden mutexes) It's not just ISRs, priority inversion is a real problem that results in some of the hardest bugs to find (I once had to chase one that happened only once a month, resulting in satellite systems losing their provisioning)
- erichocean 10y ago>I was kind of pointing out that people know that mutexes in ISRs are a bad idea, but don't know as much about the other dragons that live in the same swamp Honestly, these "people" seem like mythical creatures to me; I've certainly never met one. If you're qualified to write an ISR in C++, you're qualified to understand which parts of C++ are valid to use in an ISR and which aren't. This is a non-problem that does not appear in practice, even though it could in theory.
- Kenji 10y agoThe usage of single throw statement in the source code will result in more than 120KB of extra binary code in the final binary image. Just try it yourself with your compiler and see the difference in size of the produced binary images. What?? 120KB? I have to try that out right away. Edit: That turned out to be completely wrong. Simple program without throw: 71'218 bytes. With throw (one additional line that throws a plain integer): 71'814 bytes. GCC 4.8.1 on Windows. Would have been surprised if that was true. Edit2: Okay, my bad, I should have linked statically. The statement sounded so absolute, but of course it is conditioned on the bare metal environment which is the subject of this article. Thanks for pointing out where I went wrong.
- WalterBright 10y agoThe exception handling code in the GCC library is a lot more than 600 bytes. But if you were linking with the shared library, it won't be reflected in the size of the executable. Linking with the static library may show a quite different story.
- deleted 10y ago[deleted]
- mattkrause 10y agoEven when linked statically, my "Hello World" program is only 10,332 bytes larger than something which prints "Hello World" and then throws an integer. Building the no exceptions version with -fno-exceptions doesn't change the size of the exception-free version either. (g++ 4.8.5 with -Os)
- WalterBright 10y agoAll functions get compiled with exception handling unwind data, so you're going to get that pulled in whether the executable throws or not. In order to not get that, you'll likely have to rebuild the entire runtime library with EH turned off.
- firat 10y ago
- Animats 10y agoThe Arduino development environment is really GCC C++ with a platform-specific library. All the compile-time C++ features work. Some features that need run-time support may not link.
- devbent 10y agoIf you go down to micro-controller levels, you often times are stuck with C++ 2003 and a vendor specific compiler, which means you will lack many of the niceties in the article. I agree with him that removing the entire standard library is needed. Of course you then need to copy an implementation of printf from somewhere, and likely set it up to only work in your debug builds. Then you quickly figure out that the standard library has a lot of things you didn't even realize you depended on. Math functions typically pop up next, you'll likely end up using a vendor library (by which I mean ARM's), but if you are doing a bunch of math heavy work, and even more so if your chip has some limited FP capabilities (assuming it has an FPU at all), you may also find the need to re-implement some functions based on your performance needs. Embedded is fun. :) All that said, I would kill for access to proper lambdas.
- taneq 10y ago> If you go down to micro-controller levels, you often times are stuck with C++ 2003 This makes me feel so old. Back when I started, C on a micro-controller was a rare treat and most things were done in some obscure chip-specific assembler. I had a play with an Arduino knockoff a few weeks ago, kids these days don't know how good they've got it!
- adrianN 10y agoMore like a partially supported C++98 and a compiler with a bunch of bugs that force you to use only half of that.
- amaks 10y agoRisking being down voted, I doubt that c++ is the right language for bare metal development at all with its constraints like exceptions and RTTI. Rust seems to be the modern and safer version of C that is more appropriate for bare metal development.
- jguegant 10y agoR̟̞̣͕̣͋̄̾̔ͭṷ͇̞̘͉ŝ̹̬ͮ̂̐ͭ̌ͯtw̦̏͒͗í͒̏̄n͉̖͋ͥ̒̒̚͞n͈̣̘̿ͪͭè̡ͤͬ̔ͭ́ͦr̭͌̿̈́ͦ͑͗s̛͈̣̱̱̦͗ͨͫͥ,̪͚̙̖̥̊͟ ̘̺̦̱̭͍͊ͬ̀̚t̰̖̤̩̱̥̐̌̄̔͐̚h̲̬̲ͤ͗̓ͫ́ͪ͠e̝̜̺̟̠̿̀̚y̼̲͌̑ͭ̄͞ ͊͐͗͋͡a̬̘̮r̰̬̉ͦ͗͐̃͠e͍ͧ͊̾ͮ͗̓͜ ̨̮͕̠̓ͫͮ́͋̑͌c̳̭̪̤͌ͧ͐̇̾ͬ̒ȏ̱̰͓͓̞̰m͚̺̤̪͚͊ͧḯ̜̙͔̗̮̻ͪ̓̓n̵̬̫͔̘̰͎͌̒ͫ͛̎̇̾g̮͇̼͖͇̊̍͒̿̑!̙͞ More seriously, the problems (exceptions and rtti) that you are mentioning are actually explained in this tutorial. One can disable them and still enjoy a great part of C++. Rust might be better on some other features though.
- pjmlp 10y agoFor that Rust still needs to win the hearts of all those manufacturers selling hardware development kits. Most of us just get to use the toys already in the package and aren't allowed to bring new ones to the party.
- 0xcde4c3db 10y agoArchitecture support is lacking so far compared to gcc/g++. ARM counts for a lot, but it's still far from 100% of the embedded world.
- _pmf_ 10y agoTemplate oriented programming is a tremendously useful technique for working with overhead-less abstractions for embedded software, but C++ makes it so hard. Most large users of template oriented development (automotive) use external code generators for what should ideally be supported by the language itself.