Windows VS 2022 compilation fails

[eziochiu]

Visual Studio 2022 (v143)
ISO C++17 standard (/std:c++17)

make vs2022 MODERN_WIN_API=1 NO_USE_PORTAUDIO=1 ARCHITECTURE=_x64 NOWERROR=1

compile X64 DEBUG Version

Error C2440: "": Cannot convert from "nullptr" to "uintptr_t"
Error C2672: "std::make_pair": No matching overloaded function found

[cuavas]

You know, we might have a chance of investigating if you actually gave the location for the error, as well as the git revision you’re trying to compile.

[eziochiu]

You know, we might have a chance of investigating if you actually gave the location for the error, as well as the git revision you’re trying to compile.

master

4>drcbec.cpp
4>D:\repo\mame\src\lib\util\mfpresolve.h(78,89): error C2440: "": Cannot convert from "nullptr" to "uintptr_t"
4>D:\repo\mame\src\lib\util\mfpresolve.h(78,15): error C2672: "std::make_pair": No matching overloaded function found
4>drcbeut.cpp
4>drccache.cpp
4>drcfe.cpp
4>drcuml.cpp
4>uml.cpp
4>x86log.cpp
4>D:\repo\mame\src\lib\util\mfpresolve.h(99,89): error C2440: "": Cannot convert from "nullptr" to "uintptr_t"
4>D:\repo\mame\src\lib\util\mfpresolve.h(99,15): error C2672: "std::make_pair": No matching overloaded function found
4>D:\repo\mame\src\lib\util\mfpresolve.h(78,89): error C2440: "": Cannot convert from "nullptr" to "uintptr_t"
4>D:\repo\mame\src\lib\util\mfpresolve.h(78,15): error C2672: "std::make_pair": No matching overloaded function found
4>drcbearm64.cpp
4>D:\repo\mame\src\lib\util\mfpresolve.h(99,89): error C2440: "": Cannot convert from "nullptr" to "uintptr_t"
4>D:\repo\mame\src\lib\util\mfpresolve.h(99,15): error C2672: "std::make_pair": No matching overloaded function found
4>D:\repo\mame\src\lib\util\mfpresolve.h(78,89): error C2440: "": Cannot convert from "nullptr" to "uintptr_t"
4>D:\repo\mame\src\lib\util\mfpresolve.h(78,15): error C2672: "std::make_pair": No matching overloaded function found
4>drcbex64.cpp
4>D:\repo\mame\src\lib\util\mfpresolve.h(99,89): error C2440: "": Cannot convert from "nullptr" to "uintptr_t"
4>D:\repo\mame\src\lib\util\mfpresolve.h(99,15): error C2672: "std::make_pair": No matching overloaded function found
4>D:\repo\mame\src\lib\util\mfpresolve.h(78,89): error C2440: "": Cannot convert from "nullptr" to "uintptr_t"
4>D:\repo\mame\src\lib\util\mfpresolve.h(78,15): error C2672: "std::make_pair": No matching overloaded function found

[cuavas]

GCC and clang both treat uintptr_t(nullptr) as reinterpreting a null pointer-to-data as an unsigned integer.

For some reason, MSVC does treat (uintptr_t)nullptr as reinterpreting a null pointer-to-data as an unsigned integer: https://godbolt.org/z/W43jWKPP1

Why is MSVC not following the convention? Why is it treating a function-style cast differently to a C style cast in this case?

Can you just use clang with Visual Studio instead so you’re using a more widespread (and much faster) compiler, and you aren’t exposed to weirdness like this?

[eziochiu]

GCC and clang both treat uintptr_t(nullptr) as reinterpreting a null pointer-to-data as an unsigned integer.

For some reason, MSVC does treat (uintptr_t)nullptr as reinterpreting a null pointer-to-data as an unsigned integer: https://godbolt.org/z/W43jWKPP1

Why is MSVC not following the convention? Why is it treating a function-style cast differently to a C style cast in this case?

Can you just use clang with Visual Studio instead so you’re using a more widespread (and much faster) compiler, and you aren’t exposed to weirdness like this?

Since I need to use some of MSVC's advanced debugging features in the debug version, but prefer Clang for the release version, is there any way to solve this problem?

[cuavas]

If the “advanced features” come at the cost of needing to avoid a bunch of language features and work around bugs and unconventional behaviour, is it really a worthwhile trade-off? I’ve long maintained that Microsoft’s compiler team’s time would be better spent making their compiler actually work rather than trying to add more “advanced features”.

[npwoods]

Since I need to use some of MSVC's advanced debugging features in the debug version, but prefer Clang for the release version, is there any way to solve this problem?

Use clang for MSVC - you get to use a better compiler and a decent debugger at the same time

https://learn.microsoft.com/en-us/cpp/build/clang-support-msbuild?view=msvc-170

[yz70s]

There is a bug report about this
https://developercommunity.visualstudio.com/t/C2440-with-function-style-cast-from-null/10845354

[pmackinlay]

Thank you @yz70s; for anyone else that cares about this issue, please feel free to upvote using the link provided. I understand vote counts are a factor in determining priority.