[Openmp-dev] Location for omptarget

[Hahnfeld, Jonas via Openmp-dev]

> -----Original Message-----
> From: C Bergström [mailto:cbergstrom at pathscale.com]
> Sent: Friday, September 30, 2016 8:18 AM
> To: Hahnfeld, Jonas
> Cc: Narayanaswamy, Ravi; LLVM-OpenMP (openmp-dev at lists.llvm.org)
> Subject: Re: [Openmp-dev] Location for omptarget
> 
> On Fri, Sep 30, 2016 at 2:05 PM, Hahnfeld, Jonas via Openmp-dev <openmp-
> dev at lists.llvm.org> wrote:
> > Hi,
> >
> >
> >
> > I’m fine with putting libomptarget next to libomp as they are both
> > clearly related to each other and to OpenMP.
> >
> >
> >
> > However, I wonder whether it might be a good idea to move both under
> > the umbrella of parallel-libs in the long term.
> >
> > We can still keep the subdomain or make it a redirect, but if LLVM has
> > a collection of “parallel-libs” I think the OpenMP runtime libraries
> > should join the fun.
> 
> Non-binding votes
> 
> I'm +1 for libomptarget to be named liboffload and made a generic new
> project. I could potentially help contribute to this. Even if it starts only with a
> dependency on tasking, the future direction is clear.
> 
> I'm -1 for libomptarget to be named something confusing or which isn't
> generic

We already have "liboffload", I don't think that’s a clever name... I'm fine with "libomptarget" but I don't really care too much about the name.

> 
> I'm -1 for inclusion with "parallel-libs". I'm not sure what the current
> leadership in that project intends to do. Moving here later is much easier
> than trying to extract it out and pick-up broken pieces.
> 
> +0 libomptarget to be bundled inside OMP and stay OMP specific. Yay
> for code duplication...
> 
> >
> >
> >
> > Just my opinion,
> >
> > Jonas
> >
> >
> >
> > From: Openmp-dev [mailto:openmp-dev-bounces at lists.llvm.org] On
> Behalf
> > Of Narayanaswamy, Ravi via Openmp-dev
> > Sent: Thursday, September 29, 2016 6:56 PM
> > To: openmp-dev
> > Subject: [Openmp-dev] Location for omptarget
> >
> >
> >
> > Hi,
> >
> >     I would like to re-start the discussion on the location for omptarget.
> > The code for omptarget is under review.  We would like to make
> > progress getting this code into llvm.
> >
> > Currently we (IBM, Intel, AMD, ANL) have agreed that the right
> > approach is to make  omptarget as a subproject of openmp.  The reason
> > behind this is that omptarget is dependent on openmp tasking to handle
> > the scheduling of target task which have depend/nowait clause.  In the
> > future we could move parts of omptarget to different subproject ie
> > parallel-libs if we have clients wanting to offload and would like to
> > reuse code existing in omptarget.  We like to hear from developers
> > about the direction we want to take.
> >
> > Thanks
> >
> > Ravi Narayanaswamy.
> >
> >
> > _______________________________________________
> > Openmp-dev mailing list
> > Openmp-dev at lists.llvm.org
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev
> >
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5868 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/openmp-dev/attachments/20160930/5a13f51e/attachment-0001.bin>