To Int or to Uint, This is the Question

on YouTube ↗01h 01m

" summary

Choosing signed vs unsigned changes generated code and runtime: dividing (a+b)/2 yields a different sequence of instructions because signed arithmetic extracts the sign bit and uses arithmetic shifts while unsigned uses logical shifts; summing an arithmetic series compiles to a closed-form for signed but stays a loop for unsigned and thus one version shows 40× faster behavior; the reason is compilers can exploit or must guard against undefined behavior; practical fixes include overflow sanitizers and build flags plus helpers like size_t/ssize_t and make_signed/make_unsigned on x86.

AI-written summary · about

" chapters (12)

1. 0:00Introduction
2. 2:11Int and uint matter in C++
3. 6:06Signed vs unsigned performance
4. 15:25How integers are stored
5. 24:20Pitfalls of mixing types
6. 33:45Arithmetic series performance
7. 37:58Undefined behavior and optimizations
8. 41:55Compiler improvements and flags
9. 44:47C++11 helpers for types
10. 46:39Safe comparison functions
11. 48:05Best practices for type safety
12. 50:34Summary

" related talks

• 05mSigned Integers: Faster and CorrectorJohn McFarlane · CppCon 2017
• 55mClean Integral CodeWalther Zwart · Meeting C++ 2018
• 06mLightning Talk: Un-Undefining Undefined Behavior in C++Jefferson Carpenter · CppCon 2023
• 07mType punning done rightAndreas Weis · Meeting C++ 2017
• 07mThe Perils of Strict AliasingAndy Webber · CppCon 2014
• 48m[a bit noisy] Optimizing Generic AlgorithmsDenis Yaroshevskiy · Meeting C++ 2019
• 52mAdvanced SIMD Algorithms in PicturesDenis Yaroshevskiy · Meeting C++ 2023
• 38mEngineering Software Integral TypesAndrei Zlate-Podani · Meeting C++ 2018