public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jjhforrest at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53672] gcc/branches/cilkplus does not like C++ spawn (when optimized)
Date: Sat, 16 Jun 2012 08:13:00 -0000	[thread overview]
Message-ID: <bug-53672-4-BpBPdjA5BK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53672-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53672

--- Comment #6 from John Forrest <jjhforrest at gmail dot com> 2012-06-16 08:13:02 UTC ---
Balaji,

Thanks - seems to fix bug - now I can simplify my coding in various places.

John

On 15/06/12 20:46, bviyer at gmail dot com wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53672
>
> --- Comment #5 from Balaji V. Iyer<bviyer at gmail dot com>  2012-06-15 19:46:13 UTC ---
> Hello John,
>      The revision mentioned above should fix this problem.
>
> Thanks,
>
> Balaji V. Iyer.
>


  parent reply	other threads:[~2012-06-16  8:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14 15:56 [Bug c++/53672] New: " jjhforrest at gmail dot com
2012-06-14 16:56 ` [Bug c++/53672] " bviyer at gmail dot com
2012-06-14 19:22 ` jjhforrest at gmail dot com
2012-06-15  6:57 ` jjhforrest at gmail dot com
2012-06-15 19:44 ` bviyer at gcc dot gnu.org
2012-06-15 19:46 ` bviyer at gmail dot com
2012-06-16  8:13 ` jjhforrest at gmail dot com [this message]
2012-06-16 16:08 ` jjhforrest at gmail dot com
2012-06-18  2:08 ` bviyer at gcc dot gnu.org
2012-06-18  9:59 ` jjhforrest at gmail dot com
2012-10-10 19:34 ` paolo.carlini at oracle dot com

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-53672-4-BpBPdjA5BK@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).