public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/59807] mutex misses destructor if non-function call initialization is used
Date: Wed, 29 Jan 2014 20:26:00 -0000 [thread overview]
Message-ID: <bug-59807-4-d1P2jomx1R@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59807-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59807
Kai Tietz <ktietz at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2014-01-29
Ever confirmed|0 |1
--- Comment #6 from Kai Tietz <ktietz at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #5)
> Yes, the copy in the sources needs to be fixed. Does mingw-w64 always use
> winpthread?
Sadly, no. The use of POSIX-threading is optional. That was actual the reason
why I didn't added it by default. We would need to probe if pthread-library is
present, and just then activate enable it.
next prev parent reply other threads:[~2014-01-29 20:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 15:30 [Bug libstdc++/59807] New: " ahanins at gmail dot com
2014-01-14 15:33 ` [Bug libstdc++/59807] " ahanins at gmail dot com
2014-01-14 17:19 ` redi at gcc dot gnu.org
2014-01-14 17:22 ` redi at gcc dot gnu.org
2014-01-29 19:03 ` ahanins at gmail dot com
2014-01-29 19:53 ` redi at gcc dot gnu.org
2014-01-29 20:26 ` ktietz at gcc dot gnu.org [this message]
2014-01-30 7:32 ` ahanins at gmail dot com
2014-10-14 12:38 ` redi at gcc dot gnu.org
2014-10-14 13:09 ` ktietz at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-59807-4-d1P2jomx1R@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).