> Good luck ensuring those guarantees across all these compilers, and it is only a partial list.

Why would you need to? Build your binary, test it, give it to your customers. Why do you have to test every compiler?

Because you actually need to use those compilers to sell your software?!

For example your carefully written C++ code with gcc, might crash and burn with the TI compiler that is the only way to target a specific SOC.

Or maybe that other customer doing HPC only accepts your code if compiled with Intel or IBM compilers.

> Or maybe that other customer doing HPC only accepts your code if compiled with Intel or IBM compilers.

Then you build it, test it and deploy it. No clue what you are on about.

Because most likely you lack the experience to what actually means writing portable C++ across several OSes with disparate C and C++ compiler toolchains.

Check Boost's codebase as an example of such portability efforts.