public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/67408] <mutex> assumes that __gthread_mutex_t and__gthread_recursive_mutex_t are the same types Date: Tue, 01 Sep 2015 15:22:00 -0000 [thread overview] Message-ID: <bug-67408-4-y4gmAzy3I8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67408-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67408 --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- Created attachment 36277 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36277&action=edit Handle recursive mutexes with different types. Or this, which is probably easier on the compiler.
next prev parent reply other threads:[~2015-09-01 15:22 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-31 11:29 [Bug libstdc++/67408] New: " sebastian.huber@embedded-brains.de 2015-09-01 14:49 ` [Bug libstdc++/67408] " redi at gcc dot gnu.org 2015-09-01 14:50 ` redi at gcc dot gnu.org 2015-09-01 15:18 ` redi at gcc dot gnu.org 2015-09-01 15:22 ` redi at gcc dot gnu.org [this message] 2015-09-01 15:37 ` sebastian.huber@embedded-brains.de 2015-09-01 15:39 ` redi at gcc dot gnu.org 2015-09-02 8:43 ` sebastian.huber@embedded-brains.de 2015-09-02 10:16 ` redi at gcc dot gnu.org 2015-09-02 10:45 ` sebastian.huber@embedded-brains.de 2015-09-02 10:51 ` redi at gcc dot gnu.org 2015-09-02 10:54 ` redi 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-67408-4-y4gmAzy3I8@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: linkBe 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).