Subject: Re: [boost] [threadpool] new version v12
From: vicente.botet (vicente.botet_at_[hidden])
Date: 2008-11-04 10:33:51
----- Original Message -----
From: "Giovanni Piero Deretta" <gpderetta_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Monday, November 03, 2008 4:21 PM
Subject: Re: [boost] [threadpool] new version v12
> Not really. Without compiler help (available on VC++ but not on GCC)
> there is no way out.
>
> See:
> http://www.crystalclearsoftware.com/soc/coroutine/coroutine/coroutine_thread.html
>
> for an explaination of the problem.
The __thread bug on gcc with -o1 optimization is not enough convincing to
me.
Some TSS usage could be more dangerous when the task migrate but not all. Is
for this raison that the user must be able to forbid this migration, and
otherwise use fibers/continuations specific data instead of thread specific
data.
Of course the locking issue is a real problem. Is for this reason that I
think that either for coroutines or fibers we need to explore different
synchronization mechanisms and discourage the use of synchronization at the
thread level.
_____________________
Vicente Juan Botet Escribá