This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: Cilk Library
- From: "Iyer, Balaji V" <balaji dot v dot iyer at intel dot com>
- To: Jeff Law <law at redhat 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: Wed, 23 Oct 2013 14:10:16 +0000
- Subject: RE: Cilk Library
- Authentication-results: sourceware.org; auth=none
- References: <BF230D13CA30DD48930C31D4099330003A47B9F3 at FMSMSX101 dot amr dot corp dot intel dot com> <525460A9 dot 2040409 at redhat dot com> <BF230D13CA30DD48930C31D4099330003A48660C at FMSMSX101 dot amr dot corp dot intel dot com> <525DA223 dot 3010607 at redhat dot com> <BF230D13CA30DD48930C31D4099330003A488B2C at FMSMSX101 dot amr dot corp dot intel dot com> <52675B4D dot 20905 at redhat dot com>
> -----Original Message-----
> From: Jeff Law [mailto:law@redhat.com]
> Sent: Wednesday, October 23, 2013 1:15 AM
> To: Iyer, Balaji V; gcc@gcc.gnu.org
> Cc: Aldy Hernandez (aldyh@redhat.com); rth@redhat.com; Jason Merrill
> (jason@redhat.com)
> Subject: Re: Cilk Library
>
> On 10/16/13 13:30, Iyer, Balaji V wrote:
> >> First, the all issues Joseph mentioned need to be addressed. So
> >> first, you need to ensure it's only being built on x86/x86_64 given
> >> the asms and bring together some documentation as to what's needed to
> port the
> >> runtime system to other architectures. Closely related, I think you
> >> initially need to ensure it only builds on x86-linux platforms --
> >> unless you've already verified it works properly on one or more of
> >> the bsd platforms, solaris, windows, etc.
> >>
> >
> > We are in the process of addressing all these. I will send out an email with the
> fixed runtime as soon as I can.
> Excellent. THanks.
>
>
> >> I would strongly echo Joseph's recommendation to ensure that only
> >> those symbols specifically intended to be part of the public
> >> interface are exported from the shared library. How stable has the exported
> API/ABI
> >> for Cilk+ been? Related: how clean is the RTS from a compile-time
> >> namespace pollution standpoint. For C++ is everything in a
> >> namespace, for C is everything prefixed appropriately?
> >>
> >
> > We are currently verifying those and making sure only the required symbols
> are exported.
> IMHO, the best way to do this is with linker scripts and it's an excellent time ot
> drop in versioning information. I'd think this would be useful for ICC as well.
> This is probably the biggest issue. I'll note Richi chimed in on this as well.
>
Yup we have implemented versioning. Also, we have just completed all the things that Joseph Myers mentioned and are in the process of testing it. I will send out a revised patch this week itself.
> Look at libatomic/libatomic.map and how that gets used. It gives you full
> control over the exports.
>
> jeff