ABataev added a comment. In D83268#2135951 <https://reviews.llvm.org/D83268#2135951>, @jdoerfert wrote:
> > I don't think gcc can be using this runtime library for nvptx. > > Yes, and: We are (going to) use clang specific intrinsics to avoid CUDA > (soon). > > > Use of the new library with the previous version of the compiler. > > Except that you cannot generally expect this to work. In our supported use > case the library is kept as bitcode (LLVM-IR). Bitcode is not backward > compatible. An old toolchain (clang, llvm-link, ...) cannot be fed new IR and > be expected to work. So, we are already not able to give a stability > guarantee here, why pretend we do. The bitcode runtime has to be kept in-sync > with the toolchain. There is still compatibility between clang10 and clang11. Or they are incompatible in LLVM IR level? Also, there was a mode (I don't remember if it was removed or not) where the runtime library could be linked as `.a` library, without LLVM IR inlining. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D83268/new/ https://reviews.llvm.org/D83268 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
