Primarily because linking MSVC object files to Clang executable do not seem to be possible anymore.
But there's even 25% boost comparing to MSVC for SHA-256 and AES SW (Argon not measured)
AES NI won't compile without huge changes (alignment, partial reimplementation in asm), which hopefully won't be needed on 64-bit (and inline asm is allegedly not even possible with 64-bit Clang).
So sticking with MSVC for now.
With the changes similar boost as with Clang. Though -O3 optimization (BCC_OptimizeMaximum) was needed. Without it, the speed was 10x slower.
Source commit: 07d16b2a5ebf3b166af572a76fdbab6c488cc00f
VS2022 installs to 64-bit Program files. Builds Tools and Agent still installs to 32-bil. But Agent is 64-bit actually, what breaks some advanced P/Invoke. For now, explicitly targeting 32-bit as a workaround.
Getting rid of VS2017 Build Tools dependency in puttyvs, by re-targeting the project.
Reusing buildenv.bat in Packages-make.bat
Source commit: f79e09f3529cc9e649741772bd8ecfabed3ecb2d
