public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bviyer at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/59384] Cilk Plus array notation with for loop after segfaults
Date: Tue, 07 Jan 2014 16:06:00 -0000	[thread overview]
Message-ID: <bug-59384-4-ZxuvAYva6u@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59384-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Balaji V. Iyer <bviyer at gmail dot com> ---
Hi Nick,
     I am sorry for taking a while to get back to you. As you can tell from
gcc-patches mailing list, we are actively pursuing to try and push Cilk
Plus into trunk. We have submitted a updated patch for _Cilk_for for review
for trunk in this thread (
http://gcc.gnu.org/ml/gcc-patches/2014-01/msg00235.html).

I looked at this bug and it looks like this bug does not appear if you use
_Cilk_for implementation in the thread mentioned above.

Thanks,

Balaji V. Iyer.

PS. The code snippet could have a race-condition. I think if you switch the
for and _Cilk_for the race might go away.


On Mon, Dec 16, 2013 at 6:09 AM, nick.tomlinson at arm dot com <
gcc-bugzilla@gcc.gnu.org> wrote:

> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59384
>
> Nick Tomlinson <nick.tomlinson at arm dot com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>              Target|                            |x86_64
>                Host|                            |x86_64
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>


  reply	other threads:[~2014-01-07 16:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-04 15:41 [Bug other/59384] New: " nick.tomlinson at arm dot com
2014-01-07 16:06 ` bviyer at gmail dot com [this message]
2014-01-22 14:19 ` [Bug other/59384] " nick.tomlinson at arm dot com
2014-01-22 16:04 ` bviyer at gmail dot com
2014-01-24 12:46 ` nick.tomlinson at arm dot com
2014-01-24 12:48 ` nick.tomlinson at arm 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-59384-4-ZxuvAYva6u@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).