<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1250">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi Steve,<br>
<br>
We have a patch currently being reviewed which adds support for the basic !$omp simd directive. The plan is to merge this soon (before next Wednesday) if there are no major concerns. This can affect the limitations section which mentions no support for the
simd directive.<br>
<br>
<a href="https://github.com/flang-compiler/flang/pull/660" id="LPlnk">https://github.com/flang-compiler/flang/pull/660</a><br>
<br>
Thanks,<br>
Kiran</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> flang-dev <flang-dev-bounces@lists.llvm.org> on behalf of Steve Scalpone via flang-dev <flang-dev@lists.llvm.org><br>
<b>Sent:</b> 28 October 2020 03:11<br>
<b>To:</b> flang-dev <flang-dev@lists.llvm.org><br>
<b>Subject:</b> [flang-dev] [Classic Flang] OpenMP Compilers and Tools web page</font>
<div> </div>
</div>
<style>
<!--
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Calibri",sans-serif}
a:link, span.x_MsoHyperlink
{color:#0563C1;
text-decoration:underline}
span.x_EmailStyle17
{font-family:"Calibri",sans-serif;
color:windowtext}
.x_MsoChpDefault
{font-size:12.0pt;
font-family:"Calibri",sans-serif}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.x_WordSection1
{}
-->
</style>
<div lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="x_WordSection1">
<p class="x_MsoNormal"><span style="font-size:11.0pt">Every year, the OpenMP Language Committee solicits updates for the OpenMP Compilers and Tools web page.</span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt"> </span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt">You can see the entry for Classic Flang here:</span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt"><a href="https://docs.google.com/document/d/1y-DVSSp4UB-rJ0oQdMNLThCoqRoxG-XMY0DlTu6o7zk/edit?usp=sharing">https://docs.google.com/document/d/1y-DVSSp4UB-rJ0oQdMNLThCoqRoxG-XMY0DlTu6o7zk/edit?usp=sharing</a></span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt"> </span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt">I don’t recall any changes this year that would affect the status of OpenMP in Classic Flang. I suppose the vendors of Classic Flang will produce their own entry, so in a sense, the entry for Classic Flang
is redundant.</span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt"> </span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt">I propose we leave the text as is; however, we can consider editing the text or removing the entry altogether. Please reply with your ideas.</span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt"> </span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt">Thanks,</span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt"> </span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt">- Steve</span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt"> </span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt">Here is the current text:</span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt"> </span></p>
<p class="x_MsoNormal"><span style="font-size:9.0pt; font-family:"Arial",sans-serif; color:#2E2E2E">Fortran for LLVM. Substantially full OpenMP 4.5 on Linux/x86-64, Linux/ARM, Linux/OpenPOWER, limited target offload support on NVIDIA GPUs.</span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt"> </span></p>
<p class="x_MsoNormal" style="margin-bottom:15.0pt"><span style="font-size:9.0pt; font-family:"Arial",sans-serif; color:#2E2E2E">By default, TARGET regions are mapped to the multicore host CPU as the target with DO and DISTRIBUTE loops parallelized across all
OpenMP threads.</span></p>
<p class="x_MsoNormal" style="margin-bottom:15.0pt"><span style="font-size:9.0pt; font-family:"Arial",sans-serif; color:#2E2E2E">Known limitations: SIMD and DECLARE SIMD have no effect on SIMD code generation; TASK DEPEND/PRIORITY, TASKLOOP FIRSTPRIVATE/LASTPRIVATE,
DECLARE REDUCTION and the LINEAR/SCHEDULE/ORDERED(N) clauses on the DO construct are not supported.</span></p>
<p class="x_MsoNormal" style="margin-bottom:15.0pt"><span style="font-size:9.0pt; font-family:"Arial",sans-serif; color:#2E2E2E">The limited support for target offload to NVIDIA GPUs includes basic support for offload of !$omp target combined constructs.</span><span style="font-size:11.0pt"></span></p>
<p class="x_MsoNormal" style="margin-bottom:15.0pt"><span style="font-size:9.0pt; font-family:"Arial",sans-serif; color:#2E2E2E">Compile with -mp to enable OpenMP for multicore CPUs on all platforms.</span></p>
<p class="x_MsoNormal" style="margin-bottom:15.0pt"><span style="font-size:9.0pt; font-family:"Arial",sans-serif; color:#2E2E2E">Compile with -fopenmp -fopenmp-targets=nvptx64-nvidia-cuda to enable target offload to NVIDIA GPUs.</span><span style="font-size:11.0pt"></span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt"> </span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt"> </span></p>
</div>
</div>
</body>
</html>