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++/67114] [MinGW64] build failure with POSIX threads enabled Date: Tue, 04 Aug 2015 13:13:00 -0000 [thread overview] Message-ID: <bug-67114-4-Tp3hZ8WGvw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67114-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67114 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #36119|0 |1 is obsolete| | Attachment #36120|0 |1 is obsolete| | --- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> --- Created attachment 36124 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36124&action=edit Add _GLIBCXX_THREAD_ID_LESS hook for thread ID comparisons This patch preserves the existing behaviour for most targets but adds a new macro hook that can be used to define a target-specific alternative in os_defines.h This does not require any changes to pthreads-win32. Could you test it?
next prev parent reply other threads:[~2015-08-04 13:13 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-04 10:47 [Bug libstdc++/67114] New: " sliwa at ifpan dot edu.pl 2015-08-04 10:48 ` [Bug libstdc++/67114] " sliwa at ifpan dot edu.pl 2015-08-04 12:03 ` sliwa at ifpan dot edu.pl 2015-08-04 12:21 ` redi at gcc dot gnu.org 2015-08-04 13:13 ` redi at gcc dot gnu.org [this message] 2015-08-04 13:17 ` redi at gcc dot gnu.org 2015-08-04 14:45 ` sliwa at ifpan dot edu.pl 2015-08-04 15:55 ` redi at gcc dot gnu.org 2015-08-05 9:55 ` sliwa at ifpan dot edu.pl 2015-08-08 22:01 ` jason at gcc dot gnu.org 2015-08-08 22:05 ` jason 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-67114-4-Tp3hZ8WGvw@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).