> Hmm ??
> What about a simple
> if (we_want_thread_safety_NOW)
>       EnterCriticalSection(...);
> .
> .
> .
> if (we_want_thread_safety_NOW)
>       LeaveCriticalSection(...);
> 
> and wine.conf parameter ?
> 
> Or does this burn still too many CPU cycles ?

It is the reentrancy protection that cost the most.
Having runtime choice of thread safety doesn't cost
very much compare to that. However if we doesn't
need reentrancy it will be noticeable, especially
if we compile with -fPIC, which we currenly do.

Reply via email to