dynare/dynare++
Sébastien Villemot 3e5b4084b8
Dynare++: fix bug in new threading code
At the end of a thread, we must first notify the main thread waiting on the
condition variable, then unlock the mutex. We must do these two operations in
that order, otherwise there is a possibility of having the main process
destroying the condition variable before the thread tries to notify it (if all
other threads terminate at the same time and bring the counter down to zero).
For that reason, we cannot use std::notify_all_at_thread_exit().

Bug introduced in commit 752a02a36.
2019-02-02 09:05:02 +01:00
..
doc Dynare++: by default, use as many threads as there are logical CPUs 2019-01-29 16:34:25 +01:00
extern Refactor GeneralMatrix and ConstGeneralMatrix classes 2019-01-24 15:27:23 +01:00
integ Dynare++: by default, use as many threads as there are logical CPUs 2019-01-29 16:34:25 +01:00
kord Dynare++ multithreading: simplification of mutex interface 2019-01-29 15:53:44 +01:00
parser/cc Dynare++: enforce C++ Emacs mode for bison/flex files 2019-01-15 19:03:58 +01:00
src Dynare++: another change related to default number of threads 2019-01-29 20:31:06 +01:00
sylv Dynare++: convert doc of Sylvester module to LaTeX 2019-01-31 12:14:12 +01:00
tests Dynare++: fixed bug in tests 2011-01-20 15:42:53 -05:00
tl Dynare++: fix bug in new threading code 2019-02-02 09:05:02 +01:00
utils/cc Various modernizations 2019-01-10 18:24:04 +01:00
Makefile.am Dynare++: remove leftover file from the transition away from CWEB 2019-01-31 19:01:40 +01:00
change_log.html Putting dynare++ under main dynare SVN repository 2009-09-08 13:55:19 +00:00