- 15 Aug, 2018 35 commits
-
-
Piotr Caban authored
Signed-off-by:
Piotr Caban <piotr@codeweavers.com> Signed-off-by:
Alexandre Julliard <julliard@winehq.org>
-
Stefan Dösinger authored
Signed-off-by:
-
Piotr Caban authored
Signed-off-by:
-
Piotr Caban authored
Signed-off-by:
-
Henri Verbeet authored
It's hard enough for a single CPU core to keep a modern GPU busy in the optimal case, but with typical batch sizes of 4 vertices and trivial shaders, our tests are extremely CPU bound. With 8+-core CPU's being generally available, there's a lot to be gained. Generally speaking, not all tests can be run in parallel; tests that touch global state, like e.g. the display mode, can't. Fortunately, none of the d3d11 tests currently do that. Unfortunately, this currently doesn't help quite as much on Wine as it does on Windows. The big wined3d lock prevents a lot of parallelism, even though the tests use separate Direct3D devices. In the specific case of these tests, simply disabling the lock is safe, and shows how much could be gained by simply pushing the lock down a layer to the device. Signed-off-by:
Henri Verbeet <hverbeet@codeweavers.com> Signed-off-by:
-
Henri Verbeet authored
Instead of hoping that 150 characters is plenty. Signed-off-by:
-
Henri Verbeet authored
Signed-off-by:
-
Henri Verbeet authored
Not all callers care. Signed-off-by:
-
Henri Verbeet authored
Instead of a wined3d_shader_instruction structure. It only uses the instruction to get at the context, so just pass the context directly. Signed-off-by:
-
Alistair Leslie-Hughes authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=45603Signed-off-by:
Alistair Leslie-Hughes <leslie_alistair@hotmail.com> Signed-off-by:
-
Aric Stewart authored
Signed-off-by:
Aric Stewart <aric@codeweavers.com> Signed-off-by:
-
Gijs Vermeulen authored
Signed-off-by:
Gijs Vermeulen <gijsvrm@gmail.com> Signed-off-by:
-
Austin English authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=45167Signed-off-by:
-
Alexandre Julliard authored
Signed-off-by: -
Alex Henrie authored
Signed-off-by:
Alex Henrie <alexhenrie24@gmail.com> Signed-off-by:
-
Jacek Caban authored
Signed-off-by:
Jacek Caban <jacek@codeweavers.com> Signed-off-by:
-
Jacek Caban authored
Signed-off-by:
-
Jacek Caban authored
Signed-off-by:
-
Jacek Caban authored
Signed-off-by:
-
Jacek Caban authored
Signed-off-by:
-
Jacek Caban authored
Signed-off-by:
-
Jacek Caban authored
Signed-off-by:
-
Jacek Caban authored
Signed-off-by:
-
Zhiyi Zhang authored
Signed-off-by:
Zhiyi Zhang <zzhang@codeweavers.com> Signed-off-by:
-
Zhiyi Zhang authored
Signed-off-by:
-
Zhiyi Zhang authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=43252Signed-off-by:
-
Daniel Lehman authored
Signed-off-by:
Daniel Lehman <dlehman@esri.com> Signed-off-by:
-
Daniel Lehman authored
Signed-off-by:
-
Michael Stefaniuc authored
Signed-off-by:
Michael Stefaniuc <mstefani@winehq.org> Signed-off-by:
-
Michael Stefaniuc authored
Signed-off-by:
-
Michael Stefaniuc authored
Signed-off-by:
-
Alexandre Julliard authored
Signed-off-by: -
Alexandre Julliard authored
Signed-off-by: -
Alexandre Julliard authored
Signed-off-by: -
Alexandre Julliard authored
gcc is now warning about this. Signed-off-by:
-
- 14 Aug, 2018 5 commits
-
-
Jon Doron authored
The utility muirct.exe for some reason accesses the opaque HANDLE that is returned by BeginUpdateResource, it assumes a certain structure in which (on 32bit systems) there is a pointer to the wide repesentation of the file name in offset 0x18 (0x30 on 64bit). Signed-off-by:
Jon Doron <arilou@gmail.com> Signed-off-by:
-
Fabian Maurer authored
Signed-off-by:
Fabian Maurer <dark.shadow4@web.de> Signed-off-by:
-
Fabian Maurer authored
The pointer is set to the required size not only when the input size is 0, but generally when it is too small. Signed-off-by:
-
Fabian Maurer authored
Currently a pointer to a local variable is passed, that causes severe stack corruption. Signed-off-by:
-
Guillaume Charifi authored
Signed-off-by:
Guillaume Charifi <guillaume.charifi@sfr.fr> Signed-off-by:
-
