Another update: there are two separate problems in LLVM which "cooperate" to lead to this bug. http://reviews.llvm.org/D22210 and http://reviews.llvm.org/D22217 fix both problems (and either is sufficient for this bug here).