> -----Original Message----- > From: gcc-patches-ow...@gcc.gnu.org [mailto:gcc-patches- > ow...@gcc.gnu.org] On Behalf Of Jeff Law > Sent: Monday, October 28, 2013 4:24 PM > To: Iyer, Balaji V; r...@redhat.com; Jason Merrill (ja...@redhat.com); Aldy > Hernandez (al...@redhat.com) > Cc: gcc-patches@gcc.gnu.org > Subject: Re: [PATCH] Cilk Keywords (_Cilk_spawn and _Cilk_sync) for C (and > C++) > > On 10/22/13 10:22, Iyer, Balaji V wrote: > > Hi Jeff, I have attached 2 patches - 1 for C and 1 for C++ - along > > with the changelogs (ChangeLog.cilkplus for C and common changes, > > cp-ChangeLog.cilkplus for C++ specific files) with the changes you > > have requested. Answers to your questions are given below also. > > > > It passes all its tests and doesn't affect any other existing tests > > (i.e. by affect I mean fail a passing test or pass a failing test). > > > > A note. cilk-common seems to be a mix of tree and rtl bits. Those may need > to > be broken into separate files and/or moved around as part of the > reorganization > work that's occurring in GCC right now. So if Andrew or someone else pings > you, please respond appropriately. > > The C (and shared) parts of this patch are OK. Jason needs to review the C++ > front-end changes. > > If possible, I recommend installing the C (and shared) bits as well as the > runtime > component if they can build & work w/o the C++ front-end changes, then track > the C++ front-end changes separately.
Thanks! I will extract and check in the Cilk_spawn and _Cilk_sync for C work. -Balaji V. Iyer. > > Jeff
