This is the mail archive of the
mailing list for the GCC project.
Re: Cilk Library
- From: Jeff Law <law at redhat dot com>
- To: "Iyer, Balaji V" <balaji dot v dot iyer at intel dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Cc: "Aldy Hernandez (aldyh at redhat dot com)" <aldyh at redhat dot com>, "rth at redhat dot com" <rth at redhat dot com>, "Jason Merrill (jason at redhat dot com)" <jason at redhat dot com>
- Date: Tue, 08 Oct 2013 13:44:41 -0600
- Subject: Re: Cilk Library
- Authentication-results: sourceware.org; auth=none
- References: <BF230D13CA30DD48930C31D4099330003A47B9F3 at FMSMSX101 dot amr dot corp dot intel dot com>
On 10/02/13 13:40, Iyer, Balaji V wrote:
Dear steering committee, To support the _Cilk_spawn, and _Cilk_sync
implementation in GCC (patch submitted link:
http://gcc.gnu.org/ml/gcc-patches/2013-09/msg00859.html), we need to
add a foreign library (Cilk Runtime Library) into the gcc repository.
With this email, I am attaching the README file that will accompany
Cilk Runtime Library (libcilkrts). I am also copy-pasting the header
comment from one of the libcilkrts files. The header shown below will
be in all the source files in libcilkrts. Does this look OK?
I'm pleased to announce the steering committee approves the license
terms for the Cilk+ runtime system as well as the plan to have the Cilk+
runtime maintained upstream by Intel and copied into the GCC repository.
Given the runtime system will be maintained upstream by Intel, only a
cursory review of the runtime system should be necessary -- basically
stuff like ensuring it integrates into our build system, copyrights are
in place and the like.