<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: arial,helvetica,sans-serif; font-size: 10pt; color: #000000'><br><hr id="zwchr"><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px; color: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"C Bergström" <cbergstrom@pathscale.com><br><b>To: </b>"Hal Finkel" <hfinkel@anl.gov><br><b>Cc: </b>"llvm-dev" <llvm-dev@lists.llvm.org>, "cfe-dev" <cfe-dev@lists.llvm.org>, "openmp-dev" <openmp-dev@lists.llvm.org>, "Chandler Carruth" <chandlerc@gmail.com>, "Carlo Bertolli" <cbertol@us.ibm.com>, "Andrey Bokhanko" <andreybokhanko@gmail.com><br><b>Sent: </b>Wednesday, June 1, 2016 12:19:19 AM<br><b>Subject: </b>Re: [Openmp-dev] [llvm-dev] [cfe-dev] RFC: Proposing an LLVM subproject for parallelism runtime and support libraries<br><br><div dir="ltr"><div id="DWT1101"><div>The thread has lost focus and cherry picking replies..<br><br>To restate things since maybe you missed my points<br>----<br></div>1) SE is a programming model and needs a home of it's own. Having a programming model with it's headers and all other stuff glued into a runtime project which intends to be universal and PM agnostic doesn't make sense.<br></div></div></blockquote>They'd start in separate subdirectories.<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px; color: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><div dir="ltr"><div></div><div><br></div><div id="DWT1103">1.1) The more I look, the most it seems SE is just a step-child project and stuffing it in llvm while still not having any users or strong backing doesn't make sense. We have enough PM already and my gut feeling is this isn't going in a direction to bring in other stakeholders.<br></div></div></blockquote>I think this is the core of my reply. OpenMP has a strong user community, but OpenMP 4 offloading is still young. OpenMP 4 offloading does not yet have a real user community yet because the first implementations just started shipping very recently. Furthermore, our implementation is certainly quite new, and OpenMP 4 offloading is really quite akin to SE in that regard. I view them both as experimental projects, and both have strong backing with significant investment, so I expect both to mature over time. Our non-subtle strategic goal as a community should be to encourage the various teams to take advantage of each others expertise in the most practical way.<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px; color: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><div dir="ltr"><div></div><div id="DWT1102"><br>2) Parallel name sucks -1, too generic. imho project is more focused on offloading. We're not proposing the whole OpenMP runtime be merged here, but just the offloading part. Yes onloading will be included, but just the generic pieces.<br></div></div></blockquote>I agree that the 'openmp' runtime project logically fits within the purview of a 'parallel' project. We may even want to move it there eventually. We might also want it to remain separate while the project uses its own coding conventions (which are different from LLVM's coding conventions for historical reasons). We're not yet had that conversation, but it is a good one to have. <br><br>Thanks again,<br>Hal<br><br>-- <br><div><span name="x"></span>Hal Finkel<br>Assistant Computational Scientist<br>Leadership Computing Facility<br>Argonne National Laboratory<span name="x"></span><br></div></div></body></html>