> But isn't this a bug in the codegen itself? This bug is in the (target-independent) IRGen part of clang. I was referring to the target-dependent stuff in LLVM that generates the machine code. This confusion is one of the reasons why I support renaming clang's part from CodeGen to IRGen ;) http://llvm-reviews.chandlerc.com/D151