public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "njs at pobox dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/60035] [PATCH] make it possible to use OMP on both sides of a fork (without violating standard)
Date: Sat, 05 Apr 2014 13:43:00 -0000 [thread overview]
Message-ID: <bug-60035-4-kPLpUnupUY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60035-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60035
--- Comment #8 from Nathaniel J. Smith <njs at pobox dot com> ---
(In reply to larsmans from comment #7)
> Phase 1? (Not familiar with the GCC dev cycle.)
Sorry, meant "stage 1". GCC trunk is (IIUC) currently in RC-bug-fixes-only
pre-release freeze mode.
http://gcc.gnu.org/develop.html
prev parent reply other threads:[~2014-04-05 13:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 22:51 [Bug libgomp/60035] New: " njs at pobox dot com
2014-02-07 5:08 ` [Bug libgomp/60035] " conradsand.arma at gmail dot com
2014-02-12 22:38 ` njs at pobox dot com
2014-02-14 0:03 ` gcc-bugs at warnes dot net
2014-04-05 12:47 ` larsmans at gmail dot com
2014-04-05 13:21 ` njs at pobox dot com
2014-04-05 13:23 ` njs at pobox dot com
2014-04-05 13:29 ` larsmans at gmail dot com
2014-04-05 13:43 ` njs at pobox dot com [this message]
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-60035-4-kPLpUnupUY@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).