- The ultimate thread pool - 5 Updates
- xchg based thing... - 1 Update
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>: Jan 26 05:15PM -0800 On 1/25/2024 8:08 PM, Bonita Montero wrote: >> [...] >> Just make sure to take the time to model it in a race detector. > Idiot ... Sigh. I don't have the time to look over your code and find any potential issues right now. I will wait for one of your infamous corrections instead. At least if you said here are some test units and they pass, well, that would be a good sign, right? :^) |
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>: Jan 26 07:23PM -0800 On 1/25/2024 8:08 PM, Bonita Montero wrote: >> [...] >> Just make sure to take the time to model it in a race detector. > Idiot ... Don't be ashamed of creating a test unit. If it find any errors, just correct them, right? Notice how I formulated my xchg algortihm in a test unit first! https://groups.google.com/g/comp.lang.c++/c/Skv1PoQsUZo/m/bZoTXWDkAAAJ No shame in that! Right? :^) |
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>: Jan 26 07:24PM -0800 On 1/26/2024 7:23 PM, Chris M. Thomasson wrote: > unit first! > https://groups.google.com/g/comp.lang.c++/c/Skv1PoQsUZo/m/bZoTXWDkAAAJ > No shame in that! Right? :^) Give it a go? https://github.com/dvyukov/relacy |
Bonita Montero <Bonita.Montero@gmail.com>: Jan 27 09:38AM +0100 Am 25.01.2024 um 20:31 schrieb Chris M. Thomasson: >> This is the implementation > [...] > Just make sure to take the time to model it in a race detector. The synchronization part is trivial. It's the state the synchronization manages that is complex. |
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>: Jan 27 01:05PM -0800 On 1/25/2024 9:25 AM, Bonita Montero wrote: > #include <functional> > #include <chrono> > struct thread_pool [...] > #pragma clang diagnostic ignored "-Wparentheses" > #pragma clang diagnostic ignored "-Wunqualified-std-cast-call" >
Subscribe to:
Post Comments (Atom)
|
No comments:
Post a Comment