- 06 Jul, 2015 3 commits
-
-
Sebastian Lackner authored
-
Sebastian Lackner authored
To implement waiting for an arbitrary number of handles, we group them in buckets up to (MAXIMUM_WAIT_OBJECTS - 1) objects, and then assign a dedicated wait queue thread. The last handle is used to notify about changes.
-
Sebastian Lackner authored
-
- 03 Jul, 2015 37 commits
-
-
Nikolay Sivov authored
-
Nikolay Sivov authored
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
Also lock/unlock the module only on creation/destruction of the object.
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
Also lock/unlock the module only on creation/destruction of the object.
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
Also lock/unlock the module only on creation/destruction of the object.
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
Also lock/unlock the module only on creation/destruction of the object.
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
Also lock/unlock the module only on creation/destruction of the object.
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
-
Józef Kucia authored
-
Józef Kucia authored
-
Józef Kucia authored
-
Józef Kucia authored
-
Matteo Bruni authored
-
Matteo Bruni authored
-
Matteo Bruni authored
-
Matteo Bruni authored
-
Matteo Bruni authored
That can only happen by manually modifying select_vertex_implementation() and select_fragment_implementation(), which may be useful for testing non-default vertex / fragment pipeline implementations.
-
Sebastian Lackner authored
-
Sebastian Lackner authored
-
Sebastian Lackner authored
-
Sebastian Lackner authored
-
Sebastian Lackner authored
-
Sebastian Lackner authored
-