search for: henlin

...en 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, &g...

Alexandre, Thanks for further shedding some light on the way OpenMP handles dependencies between tasks. I'm sorry for leaving that out of my document, it was just because I didn't know much about the way OpenMP handled its workflows. On Mon, Mar 28, 2016 at 11:43 AM Jason Henline <jhen at google.com> wrote: > Hi Carlo, > > Thanks for helping to clarify this point about libomptarget vs liboffload, > I have been getting confused about it myself. I think the open question > concerns libomptarget not liboffload (others can correct me if I have > misund...

...e detailed doc describing how StreamExecutor platforms relate to libomptarget RTL interfaces. The doc also describes why the lack of support for streams in libomptarget makes it impossible to implement some of the most important StreamExecutor platforms in terms of libomptarget ( https://github.com/henline/streamexecutordoc/blob/master/se_and_openmp.rst). When I was originally optimistic about using liboffload to implement StreamExecutor platforms, I was not aware of this issue with streams. Thanks to Carlo Bertolli for bringing this to my attention. After having looked in detail at the liboffload...

...ion of the heterogeneous approach: there should be no changes to build scripts. The resultant executable/library obtained from the build should be self-contained and user will have no extra problems with target objects/files availability at rutnime. Sergos. On Mon, Mar 28, 2016 at 9:47 PM, Jason Henline via cfe-dev < cfe-dev at lists.llvm.org> wrote: > Alexandre, > > Thanks for further shedding some light on the way OpenMP handles > dependencies between tasks. I'm sorry for leaving that out of my document, > it was just because I didn't know much about the way OpenMP...

...rget two different runtime libraries that seems to have large chunk of overlapping functionalities. On a high-level view, these libraries seems to have the same goals with respect to what they provide to the compiler. Can you elaborate? Thanks, -- Mehdi > On Mar 28, 2016, at 9:37 AM, Jason Henline via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I did a more thorough read through liboffload and wrote up a more detailed doc describing how StreamExecutor platforms relate to libomptarget RTL interfaces. The doc also describes why the lack of support for streams in libomptarget...

...ventor, Advanced Compiler Technologies > - research: compiler optimization (OpenMP, multithreading, SIMD) > - info: alexe at us.ibm.com http://www.research.ibm.com/people/a/alexe > - phone: 914-945-1812 (work) 914-312-3618 (cell) > > > ----- Original message ----- > From: Jason Henline via Openmp-dev <openmp-dev at lists.llvm.org> > Sent by: "Openmp-dev" <openmp-dev-bounces at lists.llvm.org> > To: Andrey Bokhanko <andreybokhanko at gmail.com>, Chandler Carruth < > chandlerc at google.com> > Cc: llvm-dev <llvm-dev at lists.llvm.or...

...ere > should be no changes to build scripts. The resultant executable/library > obtained from the build should be self-contained and user will have no > extra problems with target objects/files availability at rutnime. > > Sergos. > > > On Mon, Mar 28, 2016 at 9:47 PM, Jason Henline via cfe-dev < > cfe-dev at lists.llvm.org> wrote: > >> Alexandre, >> >> Thanks for further shedding some light on the way OpenMP handles >> dependencies between tasks. I'm sorry for leaving that out of my document, >> it was just because I didn't k...

Hola Chandler, On Tue, Mar 15, 2016 at 1:44 PM, Chandler Carruth via Openmp-dev < openmp-dev at lists.llvm.org> wrote: > It seems like if the OpenMP folks want to add a liboffload plugin to > StreamExecutor, that would be an awesome additional platform, but I don't > see why we need to force the coupling here. > > Let me give you a reason: while user-facing sides of

...s to build scripts. The resultant executable/library >> obtained from the build should be self-contained and user will have no >> extra problems with target objects/files availability at rutnime. >> >> Sergos. >> >> >> On Mon, Mar 28, 2016 at 9:47 PM, Jason Henline via cfe-dev < >> cfe-dev at lists.llvm.org> wrote: >> >>> Alexandre, >>> >>> Thanks for further shedding some light on the way OpenMP handles >>> dependencies between tasks. I'm sorry for leaving that out of my document, >>> it was...

...ld 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 created a GitHub repo that contains the documentation I have been creating for StreamExecutor. https://github.com/henline/streamexecutordoc It contains the design docs from the original email in this thread, and it contains a new doc I just made that gives a more detailed sketch of the StreamExecutor platform plugin interface. This shows which methods must be implemented to support a new platform in StreamExecutor,...

...e large chunk of overlapping functionalities. > On a high-level view, these libraries seems to have the same goals with respect to what they provide to the compiler. > > Can you elaborate? > > Thanks, > > -- > Mehdi > > >> On Mar 28, 2016, at 9:37 AM, Jason Henline via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >> >> I did a more thorough read through liboffload and wrote up a more detailed doc describing how StreamExecutor platforms relate to libomptarget RTL interfaces. The doc also describes w...

...in this project, even though it doesn't fit in the category of "offloading". So that is an argument in favor of "parallel_libs" instead of "offload_libs". Chandler, please correct me if I misrepresented your thoughts on this. On Thu, Apr 28, 2016 at 9:55 AM Jason Henline <jhen at google.com> wrote: > Alexandre, > > Thanks for your thoughts on this. I was thinking that each subproject > library would be responsible for handling its own name and any associated > branding. For example, when evangelizing for StreamExecutor, I plan to > refer t...

...exandre Eichenberger, Master Inventor, Advanced Compiler Technologies - research: compiler optimization (OpenMP, multithreading, SIMD) - info: alexe at us.ibm.com http://www.research.ibm.com/people/a/alexe - phone: 914-945-1812 (work) 914-312-3618 (cell) ----- Original message ----- From: Jason Henline via Openmp-dev <openmp-dev at lists.llvm.org> Sent by: "Openmp-dev" <openmp-dev-bounces at lists.llvm.org> To: Andrey Bokhanko <andreybokhanko at gmail.com>, Chandler Carruth <chandlerc at google.com> Cc: llvm-dev <llvm-dev at lists.llvm.org>, cfe-dev &l...

...in LLVM, we anticipate the project removing the need for this eventually and in the interim follow the simpler but still permissive license. Among other things, this makes it straightforward for these libraries to re-use core LLVM libraries where appropriate. On Wed, Apr 27, 2016 at 9:52 AM Jason Henline <jhen at google.com> wrote: > Andrey, > > I may have misunderstood Chandler, but I think it would be good to house > libomptarget together with SE in the new project. I suspect he means to > leave the option open for the libomptarget developers to choose the best > option...

...ct in SVN yet? > > I’ll need to do the post commit hook to the mailing lists, plus set up > mailing lists. Would anyone want to volunteer to moderate the new mailing > lists? Will you have docs that need updating or website? > > -Tanya > > On Jun 13, 2016, at 11:01 AM, Jason Henline <jhen at google.com> wrote: > > 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 >...

...e hosting location is)? Did I misunderstand something? -- Jim James Cownie <james.h.cownie at intel.com> SSG/DPD/TCAR (Technical Computing, Analyzers and Runtimes) Tel: +44 117 9071438 From: Chandler Carruth [mailto:chandlerc at google.com] Sent: Tuesday, March 15, 2016 10:44 AM To: Jason Henline <jhen at google.com>; C Bergström <cbergstrom at pathscale.com>; Cownie, James H <james.h.cownie at intel.com> Cc: llvm-dev <llvm-dev at lists.llvm.org>; cfe-dev <cfe-dev at lists.llvm.org>; openmp-dev at lists.llvm.org Subject: Re: [cfe-dev] [Openmp-dev] RFC: Proposi...

The parallel-libs LLVM subproject is now set up and ready for code development. This is the subproject that is meant to house the StreamExecutor parallel runtime library, possibly the OpenMP target runtime libraries, and other libraries devoted to handling parallelism in LLVM (see the README currently checked into the parallel-libs base directory for the project charter). The parallel-libs

I respect Hal's more tactful approach and response.. Let me play devils advocate for a minute 1) Yet another programming model - Is the advantage spelled out somewhere? (I know there are reasons, but I'd like to see a FAQ or this clearly documented. Examples pretty please.. More for long term than my own selfish benefit) 2) Is this an "open standard" - If I wanted to propose a

I think it would be great if StreamExecutor could use liboffload to perform its offloading under the hood. Right now offloading is handled in StreamExecutor using platform plugins, so I think it could be very natural for us to write a plugin which basically forwards to liboffload. If that worked out, we could delete our current plugins and depend only on those based on liboffload, and then all the