rjmccall added a comment. Okay. That raises the question of what the default semantics should be for `std::bfloat16_t`, i.e. whether we should semantically default the type to using excess-precision `float` arithmetic. If we did, we'd still be able to demote solitary `float` operations to BF16, but anything more complex than that would often force promotion without user intervention.
Of course, even if we do default the type to excess precision, we could still have a flag to disable that, and we could potentially have different default values on different targets. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D136919/new/ https://reviews.llvm.org/D136919 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
