June 3, 2012

Unit-testing llgo's runtime

It’s been a while since I last wrote, primarily because I’ve been moving house and was without Internet at home during the process. It’s back now, but now I have Diablo III to contend with.

In my previous post I mentioned that I would create a new branch for working on the llgo runtime. I haven’t done that yet, though I haven’t broken the build either. Rather, I’ve introduced conditional compilation to gollvm for builds against LLVM’s trunk where unreleased functionality is required, e.g. LinkModules. This isn’t currently being used in llgo-proper, so I’ve gotten away without branching so far.

The tag for building gollvm with unreleased functions is “llvmsvn”, so to build gollvm with LLVM’s trunk, including the LinkModules function, do the following:

curl https://raw.github.com/axw/gollvm/master/install.sh -tags llvmsvn | sh
So I didn’t break “the build”, meaning you can still build gollvm/llgo without also building LLVM from source. I did, however, break the llgo unit tests, as they are using the new LinkModules function. If you want to run the unit tests without building LLVM from source, then you can comment out the call to llvm.LinkModules in llgo/utils_test.go; of course, you should expect failures due to the runtime not being linked in, but that doesn’t involve all tests.

What else is new?
  • I announced on golang-dev a couple of weeks ago that I intend to work on getting exp/types up to snuff. I’ve moved some of the type construction code out of llgo-proper into llgo/types (a fork of exp/types), and eliminated most of the llgo-specific stuff from llgo/types. I’ll need to set aside some time soon to learn how to use Mercurial and create some changelists.
  • A few weeks ago I started playing with llgo and PNaCl, to see how hard it would be to get something running in Chrome. It works (with the IR Translator/external sandbox anyway), but then llgo doesn’t really do much at the moment.
That’s all for now.