<div dir="ltr"><div>(adding omp-dev; cfe-dev isn't the right place for this, so please don't copy on subsequent replies)</div><div dir="ltr"><br></div><div dir="ltr">OpenMP taskyield is useless, by design. It can be a no-op and there is no way to guarantee that OpenMP tasks make concurrent progress. <a href="https://github.com/mpi-forum/mpi-issues/issues/75">https://github.com/mpi-forum/mpi-issues/issues/75</a> has some context. The OpenMP committee has been discussing this a bunch recently but one proposed solution was to deprecate taskyield rather than fix it.</div><div dir="ltr"><br></div><div dir="ltr">I encourage you to discuss your requirements with vendors who supply you with hardware and/or compilers, since those companies have representatives in the OpenMP language committee.</div><div dir="ltr"><br></div><div>Jeff</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Sep 20, 2018 at 9:39 AM Dawson, Mark via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="white" lang="EN-US">
<div class="gmail-m_3352469656346808580WordSection1">
<p class="MsoNormal">While an implementation of OpenMP is *<b>allowed</b>* to insert implicit switching points in a task region (i.e., #pragma omp task), I as the developer can make use of the standard’s explicit task yielding if need be (i.e., #pragma omp
taskyield). My question is whether the Clang v5.0.0 implementation employs such implicit task yielding, or is it necessary for me to do so explicitly?<u></u><u></u></p>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1"><br>
Confidentiality Notice<br>
The information transmitted in this electronic mail (e-mail) is the property of Belvedere Trading LLC. This e-mail is intended only for the person or entity to which it is addressed and may contain material that is confidential, privileged or otherwise protected
by law. Any review, retention, retransmission, dissemination or other use of, or taking any action in reliance upon, this information by persons or entities other than the intended recipient is STRICTLY PROHIBITED. If you received this e-mail in error, please
alert the sender by reply e-mail and then delete this e-mail and any attachments in their entirety, whether in electronic or hard copy format.<br>
<br>
All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as
they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email.<br>
</font>
</div>
_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature">Jeff Hammond<br><a href="mailto:jeff.science@gmail.com" target="_blank">jeff.science@gmail.com</a><br><a href="http://jeffhammond.github.io/" target="_blank">http://jeffhammond.github.io/</a></div>