On 10/7/22 10:03, Stefan Dösinger (@stefan) wrote:
In the long run I will look into making wined3d a pe/so 32on64 aware thing. It'll matter a lot for ARM, but might also be a performance improvement for x86 32on64. In wined3d we have a few more options in part because d3d <= 11 doesn't have coherent mappings, but wined3d uses it for its own purposes.
Somewhat related to this, I had recently been thinking about trying to split up wined3d a bit more explicitly. The DLL is huge, and I think it can be difficult to understand what's done on the client and CS side, which is a pretty important distinction. I'd recently been thinking of a somewhat controversial proposal, that we might want to try splitting it into separate DLLs representing these, so that even if we don't eventually decide to split it into PE/Unix, we could have that additional clarity.
Or maybe just have a source subdirectory for the CS part?