Code Analysis ++
summary
Claims that the Clang toolchain dominates and static analysis demand is rising, and describes concrete work: data flow analysis implemented in an IDE then pushed into Clang, which detects unreachable code, dangling pointers and index-out-of-bounds with acceptable editor latency; reviews C++ Core Guidelines for which rules are toolable versus human-judged; notes growing adoption of MISRA/AUTOSAR checks in development and issues around clang-format behavior and that one third use nothing for guideline enforcement.
AI-written summary · about
chapters (12)
- 0:00Introduction and motivation
- 1:08Defining software quality
- 4:14Trade-offs and frustration
- 5:35C++ developer pain points
- 6:23Complex language issues
- 7:55Language-driven improvements
- 19:11Advanced analysis tools
- 45:19Style and syntax enforcement
- 47:30Tooling summary
- 48:43Usage statistics
- 49:56Continuous integration
- 50:54Conclusion and Q&A
related talks
01h 01mCode Analysis++
52m“Tools from the C++ eco-system to save a leg”
29m“The Current State of (free) Static Analysis"
29mUsing the Clang developer tools
55mStandard C++ Toolset
01h 01mTools from the C++ Ecosystem to save a leg
01h 32mClosing Keynote: C++ Development Tools: Past, Present and Future
54mA look at C++ through the glasses of a language tool