https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65343
--- Comment #9 from Jonathan Wakely ---
The original bug should be fixed by r13-6282-gd70f49e98245f8
Comment 8 isn't done though.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65343
--- Comment #8 from Jonathan Wakely ---
We should do something similar in src/c++11/mutex.cc
mutex&
__get_once_mutex()
{
static mutex once_mutex;
return once_mutex;
}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65343
--- Comment #7 from Jonathan Wakely ---
Great, thanks for checking it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65343
--- Comment #6 from Marc Poulhiès ---
(In reply to Jonathan Wakely from comment #5)
> Patch for stage 1:
Thank you ! I can confirm this patch fixes the issue we have on vxworks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65343
--- Comment #5 from Jonathan Wakely ---
Patch for stage 1:
--- a/libstdc++-v3/src/c++11/shared_ptr.cc
+++ b/libstdc++-v3/src/c++11/shared_ptr.cc
@@ -28,6 +28,11 @@
namespace __gnu_internal _GLIBCXX_VISIBILITY(hidden)
{
+ namespace
+ {
+
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65343
Eric Botcazou changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65343
Marc Poulhiès changed:
What|Removed |Added
CC||poulhies at adacore dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65343
--- Comment #2 from frankhb1989 at gmail dot com ---
(In reply to Jonathan Wakely from comment #1)
Maybe we want to placement-new the mutexes into a buffer so they are never
destroyed, although on mingw that will show up as leaked resources at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65343
--- Comment #1 from Jonathan Wakely redi at gcc dot gnu.org ---
Maybe we want to placement-new the mutexes into a buffer so they are never
destroyed, although on mingw that will show up as leaked resources at program
shutdown (and this is only
