- 25 Mar, 2019 2 commits
-
-
FritzFlorian committed
-
This will be used for storing thread tasks aligned in continous memory, allowing different theads to work on the data without interfearing.
FritzFlorian committed
-
- 22 Mar, 2019 2 commits
-
-
FritzFlorian committed
-
Right now no work can be spawned, we simply have a proove of concept that we start up each thread, work for the master to finish and then synchronize back to the main thread.
FritzFlorian committed
-
- 21 Mar, 2019 1 commit
-
-
FritzFlorian committed
-
- 20 Mar, 2019 5 commits
-
-
FritzFlorian committed
-
FritzFlorian committed
-
This requires the user to explicitly manage the storage duration/place of the thread local state, making a fine grained memory allocation simpler.
FritzFlorian committed -
See NOTES.md for details, basically std::thread can use dynamic memory allocation internaly and we want to prevent that.
FritzFlorian committed -
We force linker errors if the new operator is used somewhere. See NOTES.md for details.
FritzFlorian committed
-
- 19 Mar, 2019 3 commits
-
-
The local storage per thread is only a pointer, this must be assigned AFTER the local storage object has moved to it's final location (e.g. on the stack of the caller). We might even change this a little further in the future to make the location of the state object more transparent.
FritzFlorian committed -
FritzFlorian committed
-
The first draft of the internal threading component is currently only implemented using the c++11 std::thread, pthread support will be added next.
FritzFlorian committed
-
- 15 Mar, 2019 2 commits
-
-
FritzFlorian committed
-
Seperate library from other parts of project (samples, playground, testing, ...). We still are in one 'toplevel' cmake project, so we can for exmaple compile everything (library and playground) in debug mode, for simple development.
FritzFlorian committed
-