dyung wrote: > ~FWIW, I'm not sure it's the same bot but one of the Windows bots had an > outdated shell using some old utils that couldn't handle long paths. If this > isn't the same one then we might need to put in stricter safeguards for > clang-doc on windows. But on modern Windows this path should be OK.~ > > NVM, completely unrelated it seems since the other bot used MSVC. What does > SIE mean in the name of the bot? I'd like to see if I can reproduce this. > We've struggled with filenames in the past.
This bot also uses MSVC (VS2019 to be precise), although it will be changed at some point to use clang-cl as that is mainly what we are using internally these days. For reference, here is the configuration of our Windows bot: ``` Windows Server 2019 Datacenter 64-bit (10.0, Build 17763) (17763.6775) Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz (32 CPUs), ~2.4GHz 128GB Microsoft (R) C/C++ Optimizing Compiler Version 19.29.30157.0 for x64 (Visual Studio 2019 16.11.42) Microsoft (R) Incremental Linker Version 14.29.30157.0 cmake version 3.20.21032501-MSVC_2 ninja version 1.11.1 Python 3.10.5 git version 2.40.1.windows.1 ccache 4.8.3 ``` > What does SIE mean in the name of the bot? SIE in this context is just stands for "Sony Interactive Entertainment" since we manage this bot. This bot does a cross compile from a Windows host to a PS5 target triple (`-DLLVM_DEFAULT_TARGET_TRIPLE=x86_64-sie-ps5 `). https://github.com/llvm/llvm-project/pull/207476 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
