This is the mail archive of the
mailing list for the GCC project.
RE: [PATCH] Cilk Keywords (_Cilk_spawn and _Cilk_sync) for C (and C++)
- From: "Iyer, Balaji V" <balaji dot v dot iyer at intel dot com>
- To: Jeff Law <law 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>, "Aldy Hernandez (aldyh at redhat dot com)" <aldyh at redhat dot com>
- Cc: "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
- Date: Wed, 23 Oct 2013 19:46:17 +0000
- Subject: RE: [PATCH] Cilk Keywords (_Cilk_spawn and _Cilk_sync) for C (and C++)
- Authentication-results: sourceware.org; auth=none
- References: <BF230D13CA30DD48930C31D4099330003A46B6DF at FMSMSX101 dot amr dot corp dot intel dot com> <525F03CE dot 9000801 at redhat dot com> <BF230D13CA30DD48930C31D4099330003A488BAF at FMSMSX101 dot amr dot corp dot intel dot com> <52675A8D dot 9040601 at redhat dot com>
> >> Can you take a look at calls.c::special_function_p and determine if we need
> >> do something special for spawn here?
> > I will look into it and let you know.
> Any word on this?
I looked into this function and from what I can tell, it is used to mark certain functions (e.g. builtin functions) as special and thus don't do special optimizations on them like a regular function. The thing is, the spawnee (the function being spawned) can be pretty much any regular function. The compiler doesn't even touch inside the function. The compiler inserts specific Cilk function calls in the spawner and transplants the function . The only major restriction I know is that the frame pointer needs to be used and that I mark as I mentioned above.
Is there anything you were thinking about that I missed?
Balaji V. Iyer.