public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dannysmith at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/33578] __gnu_parallel::yield broken on mingw32 Date: Wed, 10 Oct 2007 23:39:00 -0000 [thread overview] Message-ID: <20071010233942.3397.qmail@sourceware.org> (raw) In-Reply-To: <bug-33578-4066@http.gcc.gnu.org/bugzilla/> ------- Comment #7 from dannysmith at gcc dot gnu dot org 2007-10-10 23:39 ------- Subject: Bug 33578 Author: dannysmith Date: Wed Oct 10 23:39:30 2007 New Revision: 129219 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=129219 Log: PR libstdc++/33578 * include/parallel/compatibility.h. Use POSIX sched_yield on __CYGWIN__ (Sleep): Add prototype for __MINGW32__. Modified: trunk/libstdc++-v3/ChangeLog trunk/libstdc++-v3/include/parallel/compatibility.h -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33578
next prev parent reply other threads:[~2007-10-10 23:39 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-09-28 0:41 [Bug libstdc++/33578] New: libstdc++ parallel mode " dannysmith at users dot sourceforge dot net 2007-10-09 22:25 ` [Bug libstdc++/33578] __gnu_parallel::yield " bkoz at gcc dot gnu dot org 2007-10-09 22:38 ` bkoz at gcc dot gnu dot org 2007-10-09 22:42 ` bkoz at gcc dot gnu dot org 2007-10-09 23:52 ` dannysmith at users dot sourceforge dot net 2007-10-09 23:54 ` dannysmith at users dot sourceforge dot net 2007-10-10 2:00 ` bkoz at gcc dot gnu dot org 2007-10-10 23:39 ` dannysmith at gcc dot gnu dot org [this message] 2007-10-16 17:24 ` [Bug libstdc++/33578] __gnu_parallel::yield means what? bkoz at gcc dot gnu dot 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=20071010233942.3397.qmail@sourceware.org \ --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).