> -----Original Message----- > From: Jason Merrill [mailto:ja...@redhat.com] > Sent: Thursday, December 5, 2013 4:00 PM > To: Iyer, Balaji V; gcc-patches@gcc.gnu.org > Cc: Jeff Law > Subject: Re: _Cilk_spawn and _Cilk_sync for C++ > > On 12/04/2013 02:45 PM, Jason Merrill wrote: > >>>> + error_at (input_location, "_Cilk_sync cannot be used > >>>> + without > >>>> enabling" > >>>> + "Cilk Plus"); > >>>> + cp_lexer_consume_token (parser->lexer); > >>>> + if (parser->in_statement & IN_CILK_SPAWN) > >>>> + parser->in_statement = parser->in_statement & > >>>> + ~IN_CILK_SPAWN; > >>> > >>> Why are you messing with in_statement in the cilk_spawn code? > >>> > >> This needed to catch cases like this: > >> > >> _Cilk_spawn _Cilk_spawn foo () > > > > Oops, I meant to say "in the cilk_sync code". Why does finding a > > _Cilk_sync end the _Cilk_spawn context? > > Ping, I think this question got lost in the discussion of the copy_body > function. >
It doesn't. I just have an if statement to clear out IN_CILK_SPAWN if it is was still enabled (more like a safety measure). I have removed it. > Jason >
