<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Verdana",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><a name="_MailEndCompose">Is there a chance of Intel moving their active development work into the LLVM OpenMP runtime project? That is, Intel is clearly doing large chunks of work behind closed doors and then trying to split things into
smaller logical patches after the fact. Why not start with developing the patches in the community in the first place? Intel would effectively get free code reviews for their work, the community would have an opportunity to participate in the development process,
and the quality of the code base and commits would improve. <o:p></o:p></a></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D">I would like to move in that direction, but changing the development approach and getting management approval for such a change is non-trivial.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal">It would be significantly lower net effort than trying to split up
<a href="http://openmprtl.org">openmprtl.org</a> snapshot deltas into logical patches. <span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D">Actually, it doesn’t work like that, rather we have a set of feature level patches from functional internal commits, so no splitting should be required
and it should be reasonably automatic (at least, so Johnny tells me, and he implemented it so should know!)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal">Community contribution would also be easier if the major development focus was directly here in the LLVM project.<o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D">I don’t really follow the logic of that. Community contribution here has been light, but what contributions there have been have been integrated
relatively fast (certainly faster than contributions of OpenMP support into the clang mainline<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D">FWIW my view is that there are probably about 50 people in the world (certainly <100) who really care about OpenMP runtime implementation and that
some reasonable proportion of those aren’t interested in either open-source or LLVM, so our “total available market” is somewhere between 25 and 50 people of whom maybe 10 are actively doing runtime development. I don’t, therefore, expect a huge community
or a lot of contributions…<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D">-- Jim<br>
<br>
James Cownie <james.h.cownie@intel.com><br>
SSG/DPD/TCAR (Technical Computing, Analyzers and Runtimes)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D">Tel: +44 117 9071438</span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Steven Noonan [mailto:steven@uplinklabs.net]
<br>
<b>Sent:</b> Friday, December 19, 2014 11:16 AM<br>
<b>To:</b> Cownie, James H<br>
<b>Cc:</b> Jack Howarth; openmp-dev@cs.uiuc.edu<br>
<b>Subject:</b> Re: [Openmp-dev] new code release of Intel(R) OpenMP* Runtime Library at openmprtl.org<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Hi Jim,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">Is there a chance of Intel moving their active development work into the LLVM OpenMP runtime project? That is, Intel is clearly doing large chunks of work behind closed doors and then trying to split things into smaller logical patches
after the fact. Why not start with developing the patches in the community in the first place? Intel would effectively get free code reviews for their work, the community would have an opportunity to participate in the development process, and the quality
of the code base and commits would improve. It would be significantly lower net effort than trying to split up
<a href="http://openmprtl.org">openmprtl.org</a> snapshot deltas into logical patches. Community contribution would also be easier if the major development focus was directly here in the LLVM project.<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">- Steven<o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Fri, Dec 19, 2014 at 2:24 AM, Cownie, James H <<a href="mailto:james.h.cownie@intel.com" target="_blank">james.h.cownie@intel.com</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal">> Exactly how does the new code release of Intel® OpenMP* Runtime Library at
<a href="http://openmprtl.org" target="_blank">openmprtl.org</a>,<br>
> announced at <a href="http://planet.clang.org" target="_blank">http://planet.clang.org</a>, compare with what is currently committed in openmp trunk<br>
> at <a href="http://llvm.org" target="_blank">llvm.org</a>?<br>
<br>
If you really want *exactly*, then diff is your friend and will be more accurate and verbose than I can possibly be. :-)<br>
<br>
So, recognizing that this is not "exactly"...<br>
<br>
The link included in that planet clang article (which points to <a href="https://www.openmprtl.org/news/new-code-release-4" target="_blank">
https://www.openmprtl.org/news/new-code-release-4</a> ) gives you the release notes, which tell you the functional aspects.<br>
<br>
My note to this list yesterday explained what is happening, and that this is not a fork; all of the code in that release will be appearing here as a series of patches, probably in the New Year, now, since many people have either already left on vacation, or
leave real soon now.<br>
<br>
So, if the idea that Intel is developing code and not showing it to you every day upsets you, you can forget that you ever saw the OpenMPrtl.org code and ignore it completely. Alternately you can think of it as a preview of developments that will be arriving
here as functional patch-sets for test and review soon.<br>
<br>
HTH<br>
<br>
-- Jim<br>
<br>
James Cownie <<a href="mailto:james.h.cownie@intel.com">james.h.cownie@intel.com</a>><br>
SSG/DPD/TCAR (Technical Computing, Analyzers and Runtimes)<br>
Tel: +44 117 9071438<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
-----Original Message-----<br>
From: <a href="mailto:openmp-dev-bounces@cs.uiuc.edu">openmp-dev-bounces@cs.uiuc.edu</a> [mailto:<a href="mailto:openmp-dev-bounces@cs.uiuc.edu">openmp-dev-bounces@cs.uiuc.edu</a>] On Behalf Of Jack Howarth<br>
Sent: Thursday, December 18, 2014 10:37 PM<br>
To: <a href="mailto:openmp-dev@cs.uiuc.edu">openmp-dev@cs.uiuc.edu</a><br>
Subject: [Openmp-dev] new code release of Intel(R) OpenMP* Runtime Library at <a href="http://openmprtl.org" target="_blank">
openmprtl.org</a><br>
<br>
Exactly how does the new code release of Intel® OpenMP* Runtime Library at <a href="http://openmprtl.org" target="_blank">
openmprtl.org</a>, announced at <a href="http://planet.clang.org" target="_blank">
http://planet.clang.org</a>, compare to what is currently committed in openmp trunk at
<a href="http://llvm.org" target="_blank">llvm.org</a>?<br>
Jack<br>
<br>
_______________________________________________<br>
Openmp-dev mailing list<br>
<a href="mailto:Openmp-dev@dcs-maillist2.engr.illinois.edu">Openmp-dev@dcs-maillist2.engr.illinois.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/openmp-dev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/openmp-dev</a><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal">---------------------------------------------------------------------<br>
Intel Corporation (UK) Limited<br>
Registered No. 1134945 (England)<br>
Registered Office: Pipers Way, Swindon SN3 1RJ<br>
VAT No: 860 2173 47<br>
<br>
This e-mail and any attachments may contain confidential material for<br>
the sole use of the intended recipient(s). Any review or distribution<br>
by others is strictly prohibited. If you are not the intended<br>
recipient, please contact the sender and delete all copies.<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
_______________________________________________<br>
Openmp-dev mailing list<br>
<a href="mailto:Openmp-dev@dcs-maillist2.engr.illinois.edu">Openmp-dev@dcs-maillist2.engr.illinois.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/openmp-dev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/openmp-dev</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
</div>
</div>
<p>---------------------------------------------------------------------<br>
Intel Corporation (UK) Limited<br>
Registered No. 1134945 (England)<br>
Registered Office: Pipers Way, Swindon SN3 1RJ<br>
VAT No: 860 2173 47</p>
<p>This e-mail and any attachments may contain confidential material for<br>
the sole use of the intended recipient(s). Any review or distribution<br>
by others is strictly prohibited. If you are not the intended<br>
recipient, please contact the sender and delete all copies.</p></body>
</html>