search for: suprojects

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

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

Hi Tanya, As discussed in the past few weeks in the llvm-dev thread “RFC: Proposing an LLVM subproject for parallelism runtime and support libraries”, we would like to start a new LLVM subproject called parallel-libs (a kind of a parallel cousin to compiler-rt), and I was told you were the one to contact in order to get it created. The charter for the project is included below. Are you able to

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

...ocess may not work as well... which others may contradict if they disagree... ;] - Patches to fix the formatting / structure should go directly to llvm-commits - Patches to add a FAQ entry to section #1 above should at least go to llvm-commits, llvmdev, and possibly a few of the mailing lists for suprojects to get wider feedback. - Patches to add a FAQ entry to section #2 above should go to llvm-commits and llvmdev. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120613/ec5a721b/attachment.html>

...> disagree... ;] >> >> - Patches to fix the formatting / structure should go directly to >> llvm-commits >> >> - Patches to add a FAQ entry to section #1 above should at least go to >> llvm-commits, llvmdev, and possibly a few of the mailing lists for >> suprojects to get wider feedback. >> >> - Patches to add a FAQ entry to section #2 above should go to >> llvm-commits and llvmdev. >> > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc...

...hers may contradict if they > disagree... ;] > > - Patches to fix the formatting / structure should go directly to > llvm-commits > > - Patches to add a FAQ entry to section #1 above should at least go to > llvm-commits, llvmdev, and possibly a few of the mailing lists for > suprojects to get wider feedback. > > - Patches to add a FAQ entry to section #2 above should go to llvm-commits > and llvmdev. > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120614/e8580ae5/attachment.ht...

...> >>> - Patches to fix the formatting / structure should go directly to >>> llvm-commits >>> >>> - Patches to add a FAQ entry to section #1 above should at least go to >>> llvm-commits, llvmdev, and possibly a few of the mailing lists for >>> suprojects to get wider feedback. >>> >>> - Patches to add a FAQ entry to section #2 above should go to >>> llvm-commits and llvmdev. >>> >> >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs....

Guys, that was very interesting and useful stuff you preached there. Mind if I make a patch to the FAQ and include it somewhere? "Q: When should I develop against a branch? A: Only if you are making really big or controversial changes. ... blah blah I am thinking that it would be highly useful for the project, if somebody (yours sincerely) took it upon himself to hunt and gather the very

...ormatting / structure should go directly to >>>>> llvm-commits >>>>> >>>>> - Patches to add a FAQ entry to section #1 above should at least go to >>>>> llvm-commits, llvmdev, and possibly a few of the mailing lists for >>>>> suprojects to get wider feedback. >>>>> >>>>> - Patches to add a FAQ entry to section #2 above should go to >>>>> llvm-commits and llvmdev. >>>>> >>>> >>>> >>>> _______________________________________________ >&...

...Patches to fix the formatting / structure should go directly to >>>> llvm-commits >>>> >>>> - Patches to add a FAQ entry to section #1 above should at least go to >>>> llvm-commits, llvmdev, and possibly a few of the mailing lists for >>>> suprojects to get wider feedback. >>>> >>>> - Patches to add a FAQ entry to section #2 above should go to >>>> llvm-commits and llvmdev. >>>> >>> >>> >>> _______________________________________________ >>> LLVM Developers mail...

On Wed, Jun 13, 2012 at 11:43 AM, Andrew Trick <atrick at apple.com> wrote: > > On Jun 13, 2012, at 7:15 AM, Sergei Larin <slarin at codeaurora.org> wrote: > > Again, this is branch code, but if I can see something wrong in platform > independent portion, I'll track it on the trunk. > > > I hate to be the one to start this thread, but I have to say it at