"Just switch the compiler", they said.
summary
Switching a compiler takes months not minutes and requires new dev environments, CI nodes and rebuilt binaries for every dependency, with real failures like a CAN message misread after moving 32→64 bit and a GUI split that stalled a year while 130 classes are refactored. Expect license hits of €3,000–€35,000 per seat, toolchain conflicts and conditional compilation hell, validate with Clang‑Tidy and UBSan and archive reproducible setups using Docker containerized builds before flipping the standard flag.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:12Reasons for switching
- 5:26Why switching is hard
- 6:49New dev environment
- 13:38Handling dependencies
- 22:05Porting to new compiler
- 28:00Common pitfalls
- 33:02Runtime issues
- 47:21Avoiding surprises
- 51:20Q&A
related talks
01h 01mBringing CLANG/LLVM To Windows
01h 00mTeaching old compilers new tricks
01h 03mBringing Clean Code to large scale legacy Applications
01h 03mto pass and return, the story of functions, values and compilers
46mHow to understand million-line C++ projects
09mRustc: How I Learned to Respect the Compiler
52mCross plattform C++ development is challenging
01h 02mBinary compatibility 100