Freestanding C++ - Past, Present, and Future
summary
Defines the portable baseline: freestanding C limits guaranteed headers to core language support while freestanding C++ adds things like type_traits, atomic, and required support for new/delete/exception/RTTI; compilers (GCC) offer -ffreestanding which disables builtin stdlib assumptions but still expects memcpy/memmove/memset/memcmp. Recommends practical tactics: supply small fallback implementations, wrap std APIs behind your namespace, and use inline namespaces or feature-test macros to select per-target behavior so libraries remain usable across embedded and OS-level toolchains.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 6:58Hosted vs. Freestanding
- 9:44Definition of Freestanding C
- 18:05Tricky Language Features
- 21:46Summary of Freestanding Today
- 24:02ffreestanding
- 29:26Substituting the Standard Library
- 33:47The Future of Freestanding
- 42:55Advice for Application Developers
- 50:42Advice for Library Developers
related talks
01h 02mEmbedded Friendly C++: Features That Make a Difference
01h 30mC++ in Constrained Environments
01h 37mPeering Forward - C++’s Next Decade
02h 02mPeering forward: C++'s next decade
01h 40mBack to the Basics! Essentials of Modern C++ Style
23mFunctional Programming in C++ (Run time vs Compile time types)
55mC++ 20 Innovations: High-Performance Cross-Platform Architecture in C++
55mC++ in the World of Embedded Systems