I have a small c++ project, it has one dependency library which is added as a git submodule and most of the remaining parts (like linkage, include directories and other configuration) is managed by cmake. Under Visual Studio cmake integration It worked quite well as long as it had msvc_x64 toolset in CMakeSettings.json. However this ..
There is CLang-CL which is a drop-in replacement for MSVC’s CL. Does anyone know how to distinguish if my code is currently compiled by clang-cl or msvc’s cl? Without passing any extra defined macros on command line. Using #ifdef _MSC_VER //….. #endif doesn’t work, both compilers define _MSC_VER. Also in regular CLang on Linux (Windows ..
Clang-CL compiler error : cannot mangle this ‘auto’ type yet Context : Clang-CL compilation attempts currently results in the following error in several of my codebases : cannot mangle this ‘auto’ type yet Because this error message does not come with a filename nor an error line, it is pretty hard to locate what code ..
I have the following line for a simple build: cl -FC "../main.cpp" /link /SUBSYSTEM:CONSOLE If there is an error in the program, I can alt/ctrl-click the error, and jump right to it. However, if I change the build line to the following, it doesn’t jump to the error, and instead pops up "../main.cpp" at the ..
I am trying the Clang-CL compiler built into VS2019 under Windows 10, but cannot see how to set the compiler options, in particular, long doubles of more than 64-bits. In the Project settings, the Platform Toolset is LLVM (clang-cl). Then in C/C++ > All Options > Additional Options I added -mlong-double-80 and compiled, but it ..
Does anyone have any performance data on clang-cl vs MSVC? I’m looking at replacing MSVC in our codebase, and was wondering if anyone had any statistics. Runtime performance. Compile time performance. Link time performance. etc. Source: Windows Que..