Jason Henline via llvm-dev
2016-Jun-16 18:05 UTC
[llvm-dev] [Openmp-dev] parallel-lib: New LLVM Suproject
Would it be parallel-libs/libomptarget/ or parallel-libs/omp/libomptarget/ To me the second way seems better because it seems likely that other OpenMP stuff could end up in there in the long run. Once we decide on which code to share, I think we will end up with new directories at the top level for those common components. On Thu, Jun 16, 2016 at 10:59 AM C Bergström <cbergstrom at pathscale.com> wrote:> On Fri, Jun 17, 2016 at 1:50 AM, Jason Henline via Openmp-dev > <openmp-dev at lists.llvm.org> wrote: > > Thanks for your help, Tanya! > > > > I haven't created the project in SVN yet. Am I able to set it up myself > on > > the LLVM servers, or does someone else need to do that part? > > > > I'll be glad to volunteer to moderate the new mailing lists. > > > > We will want a website. I think there will be a top-level docs directory > for > > the project and a docs directory for each subproject. To begin with, > > StreamExecutor will be the only subproject so the structure will look > > something like this: > > > > parallel-libs/ > > docs/ > > stream_executor/ > > docs/ > > > > Does that seem like a reasonable way to set it up? > > What will it look like when they add the liboffload from OMP? > > Would it be parallel-libs/libomptarget/ > or > parallel-libs/omp/libomptarget/ > > If there's any code in SE which is "common" and can or should be > reused to consumed - maybe give some long term consideration to > superficial refactoring. This "lib/API" design mentality is common in > llvm/clang and it would be nice if it was mirrored here. >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160616/8d2e0c84/attachment.html>
Andrey Bokhanko via llvm-dev
2016-Jun-16 18:55 UTC
[llvm-dev] [Openmp-dev] parallel-lib: New LLVM Suproject
On Thu, Jun 16, 2016 at 9:05 PM, Jason Henline via Openmp-dev < openmp-dev at lists.llvm.org> wrote:> it seems likely that other OpenMP stuff could end up in there in the long > run. >Huh? What makes you think so? Have you consulted with OpenMP developers and users? Yours, Andrey -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160616/9c405c13/attachment-0001.html>
Jason Henline via llvm-dev
2016-Jun-16 19:30 UTC
[llvm-dev] [Openmp-dev] parallel-lib: New LLVM Suproject
Hi Andrey, Sorry, I definitely misspoke when I said it was likely for OpenMP stuff to end up in this new project. I meant to say that it was possible in the long run, but there are no plans for that now. On Thu, Jun 16, 2016 at 11:55 AM Andrey Bokhanko <andreybokhanko at gmail.com> wrote:> On Thu, Jun 16, 2016 at 9:05 PM, Jason Henline via Openmp-dev < > openmp-dev at lists.llvm.org> wrote: > >> it seems likely that other OpenMP stuff could end up in there in the long >> run. >> > > Huh? What makes you think so? > > Have you consulted with OpenMP developers and users? > > Yours, > Andrey > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160616/2e9a174f/attachment.html>