clang-cl functions as drop-in replacement for msvc that would deliver
superior codegen without the need to migrate to another runtime library.
but unfortunately clang-cl is still not supported by qt (neither
officially, nor with CI build tests).

We've been waiting for clang-cl to be 100% compatible with either Clang or cl.
A third one is too much maintenance.

how realistic is it to be 100% compatible? afaict clang-cl tries to meet the sweet spot of behaving like cl, just as clang tries to behave like gcc (e.g. both identifying as the compiler that it is and as compiler that it tries to identify as).

from my experience, supporting clang-cl in a codebase that supports both mingw and msvc build, tends to be minimal effort. while being able to provide binaries that are compatible with msvc runtime and have better codegen tends to be low-effort/high-reward.
--
Development mailing list
[email protected]
https://lists.qt-project.org/listinfo/development

Reply via email to