public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "roland at gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/57740] New: C++11 std::thread not usable with static linking
Date: Thu, 27 Jun 2013 20:18:00 -0000 [thread overview]
Message-ID: <bug-57740-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57740
Bug ID: 57740
Summary: C++11 std::thread not usable with static linking
Product: gcc
Version: 4.8.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: roland at gnu dot org
Host: x86_64-linux-gnu
Created attachment 30398
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30398&action=edit
test case
This bug goes back at least to 4.6, but I don't really care about anything
older than 4.8.
On x86_64-linux-gnu (and others), the attached test works when compiled with:
g++ -std=c++0x -pthread std_mutex.cc -o std_mutex
but when compiled with:
g++ -std=c++0x -static -pthread std_mutex.cc -o std_mutex
it either throws an error or just crashes.
The underlying problem is excessive use of weak references in gthr-posix.h.
I already have a fix and a testsuite addition in hand and will post them to
gcc-patches soon.
next reply other threads:[~2013-06-27 20:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 20:18 roland at gnu dot org [this message]
2013-06-27 20:20 ` [Bug libstdc++/57740] " pinskia at gcc dot gnu.org
2013-06-27 20:30 ` roland at gnu dot org
2013-06-27 20:44 ` jakub at gcc dot gnu.org
2013-06-27 20:57 ` roland at gnu dot org
2013-06-27 21:09 ` roland at gnu dot org
2013-06-27 21:15 ` jakub at gcc dot gnu.org
2013-06-27 21:25 ` roland at gnu dot org
2013-06-27 21:51 ` pinskia at gcc dot gnu.org
2013-06-27 22:12 ` roland at gnu dot org
2013-06-27 23:20 ` joseph at codesourcery dot com
2014-10-13 14:56 ` redi at gcc dot gnu.org
2014-11-04 3:32 ` mjbshaw at hotmail dot com
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-57740-4@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).