[llvm-branch-commits] [clang] [Clang] Support __bf16 type for SPIR/SPIR-V (#169012) (PR #170230)
wenju-he wrote: > Does that actually need to be backported? It seems to be a new feature and > Clang 22 will release in a couple of months. Thanks! let me double check, thanks https://github.com/llvm/llvm-project/pull/170230 ___ llvm-branch-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
[llvm-branch-commits] [clang] [Clang] Support __bf16 type for SPIR/SPIR-V (#169012) (PR #170230)
https://github.com/wenju-he closed https://github.com/llvm/llvm-project/pull/170230 ___ llvm-branch-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
[llvm-branch-commits] [clang] [Clang] Support __bf16 type for SPIR/SPIR-V (#169012) (PR #170230)
wenju-he wrote: thanks @tru for the suggestion. Close this PR. https://github.com/llvm/llvm-project/pull/170230 ___ llvm-branch-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
[llvm-branch-commits] [clang] [Clang] Support __bf16 type for SPIR/SPIR-V (#169012) (PR #170230)
wenju-he wrote: > Does that actually need to be backported? It seems to be a new feature and > Clang 22 will release in a couple of months. Thanks! @cor3ntin thanks for the suggestion. Our (Intel) GPU compiler team would appreciate that this PR can at least land on the latest already released version, which is 21.x. However, we will close this PR if it is against llvm release policy. Please advise, thanks. https://github.com/llvm/llvm-project/pull/170230 ___ llvm-branch-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
