public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/33578] __gnu_parallel::yield means what?
Date: Tue, 16 Oct 2007 17:24:00 -0000 [thread overview]
Message-ID: <20071016172406.27045.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33578-4066@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from bkoz at gcc dot gnu dot org 2007-10-16 17:24 -------
Changing this summary now that the mingw32 issue is fixed. Now, opening this
out to the implementation issues...
--
bkoz at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
GCC host triplet|i686-pc-mingw32 |all
GCC target triplet|i686-pc-mingw32 |all
Summary|__gnu_parallel::yield broken|__gnu_parallel::yield means
|on mingw32 |what?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33578
next prev parent reply other threads:[~2007-10-16 17:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 0:41 [Bug libstdc++/33578] New: libstdc++ parallel mode broken on mingw32 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
2007-10-16 17:24 ` bkoz at gcc dot gnu dot org [this message]
[not found] <bug-33578-4@http.gcc.gnu.org/bugzilla/>
2023-05-16 19:41 ` [Bug libstdc++/33578] __gnu_parallel::yield means what? pinskia at gcc dot gnu.org
2023-05-16 20:24 ` 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=20071016172406.27045.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: 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).