What Every C Programmer Should Know About Undefined Behavior #3/3 - The LLVM Project Blog
In Part 1 of the series, we took a look at undefined behavior in C and showed some cases where it allows C to be more performant than "safe" languages.
What Every C Programmer Should Know About Undefined Behavior #3/3 By Chris Lattner May 21, 2011 #optimization , #Clang 13 minute read In Part 1 of the series, we took a look at undefined behavior in C and showed some cases where it allows C to be more performant than "safe" languages. In Part 2 , we looked at the surprising bugs this causes and some widely held misconceptions that many programmers have about C. In this article, we look at the challenges that compilers face in providing warnings about these gotchas, and talk about some of the features and tools that LLVM and Clang provide to he
saved by
related reading
- What Every C Programmer Should Know About Undefined Behavior #2/3 - The LLVM Project Blogblog.llvm.org
- What Every C Programmer Should Know About Undefined Behavior #1/3 - The LLVM Project Blogblog.llvm.org
- What even is compiler correctness?williamjbowman.com
- Undefined behavior, and the Sledgehammer Principle | The Pasturethephd.dev
- A Gentle Introduction to LLVM IR · mcyoungmcyoung.xyz
- Getting silly with C, part -5^-7 - lcamtuf’s thinglcamtuf.substack.com
- The Lost Art of Structure Packingcatb.org
- Effortless Performance Improvements in C++ | Julien Jorge's Personal Websitejulien.jorge.st
- Compiler Optimizations Are Hard Because They Forget - Faultlorefaultlore.com
- Destroy All Values: Designing Deinitialization in Programming Languages - Faultloregankra.github.io
- Compilers - What Every Programmer Should Know About Compiler Optimizations | Microsoft Learnlearn.microsoft.com
- ⭐️ Fast LLM Inference From Scratchandrewkchan.dev