This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/29426] [4.2 Regression] static __recursive_mutex init vs __GTHREAD_RECURSIVE_MUTEX_INIT_FUNCTION
- From: "dannysmith at users dot sourceforge dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 11 Oct 2006 20:54:32 -0000
- Subject: [Bug libstdc++/29426] [4.2 Regression] static __recursive_mutex init vs __GTHREAD_RECURSIVE_MUTEX_INIT_FUNCTION
- References: <bug-29426-4066@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #12 from dannysmith at users dot sourceforge dot net 2006-10-11 20:54 -------
(In reply to comment #4)
> - __gnu_cxx::__recursive_mutex static_mutex;
> + static __gnu_cxx::__recursive_mutex static_mutex;
I tried thaty before I submitted bug report. No dice.
(In reply to comment #11)
> 2006-10-11 Benjamin Kosnik <bkoz@redhat.com>
> PR libstdc++/29426
> * libsupc++/guard.cc (get_static_mutex): New.
> (mutex_wrapper::mutex_wrapper): Use it to get properly initialized
> recursive mutex without ordering issues.
> * src/locale_init.cc (__get_locale_mutex): No need to
> uglify. Change to get_locale_mutex.
Thanks
I submitted a bug report just before I went to bed and it was fixed in the
morning. Wow!
This fixes testsuite failures on mingw32, too. Tested with and without
-mthreads. Also tested with a pending (stage 1) patch to enable __cxa_atexit
like destruction on mingw32.
Danny
--
dannysmith at users dot sourceforge dot net changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29426