This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: FYI on private static object construction
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin-developers at cygwin dot com
- Date: Thu, 8 Aug 2002 11:27:48 -0400
- Subject: Re: FYI on private static object construction
- References: <3D527A3C.40704@hekimian.com>
- Reply-to: cygwin-developers at cygwin dot com
On Thu, Aug 08, 2002 at 10:03:40AM -0400, Joe Buehler wrote:
>It appears from discussion on the gcc list that private static
>objects in C++ functions are constructed when they are encountered
>in program flow. E.g.:
>
>So I would recommend that in Cygwin such objects be moved out of
>functions to global scope, to avoid threading issues.
What functions are you talking about? Private static functions are
unsafe in a threaded application by default.
>Gcc generates functions with "tcf" in the name (e.g. __tcf_0) for
>this sort of code, so it is easy to tell whether a particular object
>has the problem.
So, it sounds like you should be able to supply us with a list of
the offending functions.
cgf