... and looking through the bugzilla, this seems the case in bug#992429, which is duped to bug#981975, as an LLVM issue.