At this year’s LLVM Developers’ Meeting, my coworker and I gave a talk called “How to Write a Checker in 24 Hours”, about extending the Clang Static Analyzer with custom “checkers”. The video of the talk is now online, along with all the other talks.
I’m going to Apple.
This is not as exciting for me as it would be for someone else. I actually grew up in Cupertino, and I’ve interned there a few summers ago. I have a lot of respect for Apple’s emphasis on design and quality in their products (there are always exceptions, but the general trend is very good), but I haven’t been dying to work there the way some people might.
What is exciting is what I’ll be doing. As I mentioned a few weeks back, I’ve shifted away from Cocoa development and gotten involved with Clang.
In my free time, I work on the Clang open source project, mostly on the static analyzer. This is the backend behind Xcode’s wonderful “Analyze” tool, which catches path-sensitive problems like memory leaks and then shows you the path where the leak happens.
Using custom builds of the analyzer in Xcode has always been fairly easy with the
set-xcode-analyzer tool, distributed with packaged builds of the checker or hidden in the
tools/scan-build directory in the Clang source repository. But what if you want to use a custom build as your compiler?…say, to play with Automatic Reference Counting (which …
- 2011-06-20 Automatic Reference Counting