New Patches Help WineD3D Performance - Doubled FPS In Some Micro-Benchmarks

[pal666]

Just get rid of the older GPUs

i'll ask again, are you volunteering to finance replacement?

they can't flawlessly run applications or games that require Vulkan anyway.

there are tens of thousands of games which don't require vulkan

[oiaohm]

it's irrelevant, you just have to build all wine with one msvc version. i mean how in your world every c++ program works on windows?

On MS windows microsoft provides multi copies of runtime libraries built against particular versions of msvc.

https://github.com/wine-mirror/wine/blob/master/dlls/d3dx9_39/Makefile.in

Yes notice wine d3dx9_39 here does not have its own unique code wine just reuses this. MS windows developers have admitted building windows is total pain because they in fact in place built with multi versions of MSVC. So a versioned library this this one has its own set MSVC.

Yes C only code with MSVC as reactos has found allowed built all those different versioned libraries of windows with a single version of MSVC. Once you start using C++ features like classes and so on all bets are off.

The way C++ programs under windows are working is using SXS and library version number to connect to know compatible versions of libraries.

Wine does not want to have multi versions of MSVC to build with so simple solution core wine is C only. Yes dxvk libraries even that it code C++ only have C style interfaces. Of course just to be fun some of the MS windows provided libraries are not that simple.

https://github.com/wine-mirror/wine/blob/master/dlls/msvcp140/msvcp140.spec

Yes C++ provided functions that Microsoft have built with a particular version of C++.

https://github.com/wine-mirror/wine/blob/master/dlls/msvcp140/Makefile.in

Wine does not code them uniquely or build them with a particular version of C++. Instead take the kind harder solution of doing the C++ function coded in C so performed in generic I don't care what C++ version way. Yes this is slightly slower than what Microsoft does.

Now lets say someone coded msvcp... as C++ and exported directly the C++ functions instead of wine code as C and use spec file to map. You have differences in name managing between C++ versions this includes MSVC so you would be forced to use a matched compiler.

https://eli.thegreenplace.net/2011/0...es-from-a-dll/ This is from 2011. People attempting to export C++ functions built in C++ end up running into headaches and end up doing some totally horrible hacks to avoid name managling at first messing themselves over. Of course ABI changes between C++ compilers how classes are represented in memory also come back to bite.

Yes people end up restricting to C to some extent using MSVC. Yes exporting only C functions from core libraries is what Microsoft has done. But not all the libraries you have to provide are core libraries so applications work.

Wine rule that core code is C only avoids people coding stuff like msvcp140 and others in C++ directly and attempting to directly export a C++ function leading to hell.