Thanks for the quick response. I just wanted to note that the glitch is still there with llvm 3.4 trunk.