Author: Chuanqi Xu Date: 2023-07-26T15:06:13+08:00 New Revision: 3b48613f2d90bde544669437c20fcdeb01316411
URL: https://github.com/llvm/llvm-project/commit/3b48613f2d90bde544669437c20fcdeb01316411 DIFF: https://github.com/llvm/llvm-project/commit/3b48613f2d90bde544669437c20fcdeb01316411.diff LOG: [docs] [C++20] [Modules] Mark the compatiblity issue within clang-cl.exe See https://discourse.llvm.org/t/clang-cl-exe-support-for-c-modules/72257 for details. Simply, the user of clang-cl.exe can't get a good experience with C++20 modules now. While we don't have resources to support it well now, we should make it clear in the documentation. Added: Modified: clang/docs/StandardCPlusPlusModules.rst Removed: ################################################################################ diff --git a/clang/docs/StandardCPlusPlusModules.rst b/clang/docs/StandardCPlusPlusModules.rst index 51f67318501153..06609063c61c96 100644 --- a/clang/docs/StandardCPlusPlusModules.rst +++ b/clang/docs/StandardCPlusPlusModules.rst @@ -688,6 +688,14 @@ Currently, clang requires the file name of an ``importable module unit`` should This is tracked in: https://github.com/llvm/llvm-project/issues/57416 +clang-cl is not compatible with the standard C++ modules +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Now we can't use the `/clang:-fmodule-file` or `/clang:-fprebuilt-module-path` to specify +the BMI within ``clang-cl.exe``. + +This is tracked in: https://github.com/llvm/llvm-project/issues/64118 + Header Units ============ _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
