Run an LLVM Pass Automatically with Clang

April 20, 2013

In lots of research projects that I’ve worked on, I have needed to instrument programs while compiling them. Ideally, I want to do my instrumentation on big, real-world applications that assume a gcc- or g++-like command-line compiler driver in their Makefiles. While the obvious choice for this kind of instrumentation is an LLVM pass, the official docs for LLVM make running your custom pass sound tricky. According to them, you need this sort of rigmarole:

  1. Compile each source file to bitcode with clang -c -emit-llvm code.c.
  2. Run your pass by itself with opt -load -mypass < code.bc > code_inst.bc.
  3. Run the rest of the standard optimizations with opt -O3 < code_inst.bc > code_opt.bc.
  4. Compile the optimized bitcode into assembly with llc and then use your favorite assembler and linker to get the rest of the way to an executable.

This process is a pain when what you really need is to run clang, which is command-line-compatible with gcc, just with your own pass slipped in among the rest of the optimizations. Ideally, you would type clang -mypass code.c to do everything at once.

Here’s a trick to enable something like that. You can use LLVM’s pass registry to enable your pass automatically when its shared library is loaded. To do that, just put something like this at the end of your pass code:

static void registerMyPass(const PassManagerBuilder &,
                           PassManagerBase &PM) {
    PM.add(new MyPass());
static RegisterStandardPasses

where MyPass is the name of your pass class. This way, as soon as your shared library,, is linked into any LLVM-using tool, it will ask for MyPass to be run. (You can choose when the pass runs by selecting a ExtensionPointTy.)

Now, to load and register your pass, just type:

$ clang -Xclang -load -Xclang ...

and you’ll have a full-fledged compiler driver augmented with your instrumentation.

Update, October 17, 2014: As of the current release (3.5), LLVM is in the midst of a transition to a new PassManager infrastructure. The old classes have moved into a llvm::legacy namespace. Clang, however, still uses the legacy PassManager, so this technique is still the right one to use.

To explicitly use the legacy components, you may need to include a different file, llvm/IR/LegacyPassManager.h, and refer to legacy::PassManagerBase in your callback. Like so:

#include "llvm/IR/LegacyPassManager.h"
using namespace llvm;
static void registerPass(const PassManagerBuilder &,
                         legacy::PassManagerBase &PM) {

Cursory searching on the mailing lists has failed to turn up any indication of whether or when Clang might move to the new PassManager infrastructure. If you know more, I’d be interested to hear from you.