News for hackers. Stuff that matters.
Re:Practical Guide to Bare Metal C++ by jibsen on Thursday July 21, 2016 @04:06PM (#12139640)
Using mingw-w64 (GCC 6.1.0):

  g++ -Os -static -s on `int main() { }' 17.408 bytes
  g++ -Os -static -s on `int main() { throw 42; }' 139.776 bytes
Re:Practical Guide to Bare Metal C++ by kevin_thibedeau on Thursday July 21, 2016 @07:01PM (#12140646)
Which libc? You don't necessarily get as much bloat with embedded compilers and libraries.
Re:Practical Guide to Bare Metal C++ by nomel on Thursday July 21, 2016 @06:32PM (#12140513)
Now what if you use two exceptions? If there's no significant increase, then the whole point is moot.
Re:Practical Guide to Bare Metal C++ by jotux on Thursday July 21, 2016 @07:05PM (#12140663)
Not really moot. I do C++ on embedded processors with as little as 32kB of program space. Using a single exception means your code will not fit. My general rule of thumb to use full-fledged C++ is a processor with at least 256kB of program space.

Here's a comment of mine from a previous discussion: https://news.ycombinator.com/item?id=11706840

Re:Practical Guide to Bare Metal C++ by AnimalMuppet on Thursday July 21, 2016 @07:09PM (#12140687)
Not in the bare-metal environment. You may not have the memory to use one. In such a case, the increase to use two is irrelevant.