<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=iso-8859-1"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 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:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
mso-fareast-language:EN-US;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:#002052;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Verdana","sans-serif";
color:#1F497D;
font-weight:normal;
font-style:normal;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
color:#002052;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";
mso-fareast-language:EN-US;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
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=FR link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052'>Thanks for the reply Jim,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052'>Oh, bad news… I’ll have to go in depth in the source code by my own, I guess that there is nothing also on the build system itself…<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052'>I’ll analyze all that and probably come back with a proposal for code refactoring.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052'>I just have two additional questions:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052'> - what is the reason for having two different repositories existing for this OpenMP Runtime Library (this one on llvm.org and the other one on github) ?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052'> - why is the arm part not available on github?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052'>-- Hervé<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#333333;mso-fareast-language:FR'><img width=202 height=54 id="Picture_x0020_3" src="cid:image003.png@01CF3228.608D0910" alt="Description: Description: Description: Description: Description: Description: logo_big5"></span><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#333333;mso-fareast-language:FR'><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:5.0pt;font-family:"Arial","sans-serif";color:#333333;mso-fareast-language:FR'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052;mso-fareast-language:FR'>Hervé CHAUVET </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#39A9DC;mso-fareast-language:FR'>|</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052;mso-fareast-language:FR'> TINA: 042#6655 </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#39A9DC;mso-fareast-language:FR'>|</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052;mso-fareast-language:FR'> Tel: +33 476586655 </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#39A9DC;mso-fareast-language:FR'>| </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052;mso-fareast-language:FR'>Mobile: +33 616736859</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#39A9DC;mso-fareast-language:FR'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Arial","sans-serif";color:#002052;mso-fareast-language:FR'>UPD/SSCS/IQSE/CEC (Compiler Expertise Center)</span><span style='font-size:9.0pt;font-family:"Arial","sans-serif";color:#39A9DC;mso-fareast-language:FR'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:FR'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:FR'> openmp-dev-bounces@cs.uiuc.edu [mailto:openmp-dev-bounces@cs.uiuc.edu] <b>On Behalf Of </b>Cownie, James H<br><b>Sent:</b> vendredi 21 février 2014 13:56<br><b>To:</b> Openmp-dev@dcs-maillist2.engr.illinois.edu<br><b>Subject:</b> Re: [Openmp-dev] Implementation manual of Intel OMP RTL<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D'>Unfortunately there is no implementation manual. The manual provided describes the interface functions, (or, it should do), but not the details of the internal implementation.</span><span lang=EN-GB><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'> </span><span lang=EN-GB><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'>If you have suggestions on how to refactor the code to make porting easier I’d be happy to hear them.</span><span lang=EN-GB><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'> </span><span lang=EN-GB><o:p></o:p></span></p><div><p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D;mso-fareast-language:EN-GB'>-- 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)</span><span lang=EN-GB><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;mso-fareast-language:EN-GB'>Tel: +44 117 9071438</span><span lang=EN-GB><o:p></o:p></span></p></div><p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D'> </span><span lang=EN-GB><o:p></o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:EN-GB'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:EN-GB'> <a href="mailto:openmp-dev-bounces@cs.uiuc.edu">openmp-dev-bounces@cs.uiuc.edu</a> [<a href="mailto:openmp-dev-bounces@cs.uiuc.edu">mailto:openmp-dev-bounces@cs.uiuc.edu</a>] <b>On Behalf Of </b>Herve CHAUVET<br><b>Sent:</b> Friday, February 21, 2014 12:45 PM<br><b>To:</b> <a href="mailto:Openmp-dev@dcs-maillist2.engr.illinois.edu">Openmp-dev@dcs-maillist2.engr.illinois.edu</a><br><b>Subject:</b> [Openmp-dev] Implementation manual of Intel OMP RTL</span><span lang=EN-GB><o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052'>Hi all,</span><span lang=EN-GB><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052'> </span><span lang=EN-GB><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052'> Having a request for CLANG-LLVM-OPENMP support for a STMicroelectrnoics proprietary core, we are planning to port the Intel OMP RTL. I am wondering if there is any implementation manual of this library. </span><span lang=EN-GB><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052'> </span><span lang=EN-GB><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052'> In addition, since this is an additional target for this library after intel and ARM cores, maybe it’s time to think a bit to some code refactoring to support re-targeting of the library more friendly. In that sense, does anyone have some recommendations?</span><span lang=EN-GB><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052'> </span><span lang=EN-GB><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052'>Best regards,</span><span lang=EN-GB><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#002052'>--Hervé Chauvet</span><span lang=EN-GB><o:p></o:p></span></p><p><span lang=EN-GB>---------------------------------------------------------------------<br>Intel Corporation (UK) Limited<br>Registered No. 1134945 (England)<br>Registered Office: Pipers Way, Swindon SN3 1RJ<br>VAT No: 860 2173 47<o:p></o:p></span></p><p><span lang=EN-GB>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></span></p></div></body></html>