FYI on private static object construction

[Christopher Faylor]

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