This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: private static instance construction not thread-safe?
- From: Christopher Faylor <cgf at redhat dot com>
- To: joseph dot buehler at spirentcom dot com
- Cc: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 1 Aug 2002 23:37:38 -0400
- Subject: Re: private static instance construction not thread-safe?
- References: <3D47F8AF.7010805@hekimian.com>
- Reply-to: gcc-bugs at gcc dot gnu dot org
On Wed, Jul 31, 2002 at 10:48:15AM -0400, Joe Buehler wrote:
>The attached C++ generates code that is not thread-safe,
>when using the gcc 2.95 prebuilt for Cygwin and installable
>via the Cygwin installer.
>
>gcc inserts code at the top of f() to take care of construction
>of the "temp" instance, and to schedule its destruction at program
>exit time, using atexit().
>
>The code that does this is not thread-safe -- two calls to f()
>around the same time can cause double-construction, double
>calls to atexit(), etc.
>
>Is this a gcc bug, or a result of the way that the gcc I am using
>has been configured? Or is some gcc option supposed to be used
>that will take care of this?
>
>My apologies if this has been asked a million times -- I did not
>find anything in GNATS for gcc.
The non-test versions cygwin gcc 2.95 were not built with thread support
enabled.
cgf