<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)">
<!--[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:"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;}
@font-face
{font-family:"Lucida Console";
panose-1:2 11 6 9 4 5 4 2 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;}
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;}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Verdana",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">I do understand the casting solution, but I am not sure what function you are referring to in your last message.</span><br>
</a><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Can you please explain?</span><br>
<br>
<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">My proposal would be to change the interface to
<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:"Lucida Console";color:#1F497D">static char const *<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Lucida Console";color:#1F497D">__kmp_pragma(<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Lucida Console";color:#1F497D"> enum cons_type ct,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Lucida Console";color:#1F497D"> ident_t const * ident<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Lucida Console";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"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D">Which is the function in question, I believe, to be
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Lucida Console";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Lucida Console";color:#1F497D">static char const *<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Lucida Console";color:#1F497D">__kmp_pragma(<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Lucida Console";color:#1F497D"> int ct,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Lucida Console";color:#1F497D"> ident_t const * ident<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Lucida Console";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"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D">At the call site, this should still be OK, because (IIRC) C allows a silent case from an enum to an int, the hope, then, is that since inside this
function the compiler only knows that ct is an integer it won’t believe that its range is restricted, and therefore that the test is unnecessary. Of course, the compiler may still try to be cleverer than that, and to inline the function, in which case it will
notice that the only arguments passed are of type </span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Lucida Console";color:#1F497D">enum cons_type</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D">
in which case we’ll be back where we started :-(.<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">The real issue here is that we’re trying to be very conservative in this code because we’re dealing with error messages so we know something is wrong
and that might have been caused by random stores from buggy user code which could have corrupted the place we’re reading the enumeration from, but the compiler is working on the basis of optimizing correct code…<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>
<div>
<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>
</div>
<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>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<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"> Carlo Bertolli [mailto:cbertol@us.ibm.com]
<br>
<b>Sent:</b> Monday, March 2, 2015 4:16 PM<br>
<b>To:</b> Cownie, James H<br>
<b>Cc:</b> Hal Finkel; openmp-dev@dcs-maillist2.engr.illinois.edu<br>
<b>Subject:</b> RE: [Openmp-dev] Two warnings with clang 3.5 on ppc63le<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Hi Jim, Hal,</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Thanks for explaining this.</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I do understand the casting solution, but I am not sure what function you are referring to in your last message.</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Can you please explain?</span><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Thanks</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">-- Carlo</span><br>
<br>
<br>
<br>
<img width="16" height="16" id="_x0000_i1025" src="cid:image001.gif@01D05504.BDE44BF0" alt="Inactive hide details for "Cownie, James H" ---03/02/2015 06:28:19 AM---> If you'd like to prevent this, you'll need to change "><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#424282">"Cownie,
James H" ---03/02/2015 06:28:19 AM---> If you'd like to prevent this, you'll need to change the type of the variable to int > (or unsign</span><br>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif">"Cownie, James H" <<a href="mailto:james.h.cownie@intel.com">james.h.cownie@intel.com</a>></span><br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif">Hal Finkel <<a href="mailto:hfinkel@anl.gov">hfinkel@anl.gov</a>></span><br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Cc: </span>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif">Carlo Bertolli/Watson/IBM@IBMUS, "<a href="mailto:openmp-dev@dcs-maillist2.engr.illinois.edu">openmp-dev@dcs-maillist2.engr.illinois.edu</a>" <<a href="mailto:openmp-dev@dcs-maillist2.engr.illinois.edu">openmp-dev@dcs-maillist2.engr.illinois.edu</a>></span><br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif">03/02/2015 06:28 AM</span><br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject:
</span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">RE: [Openmp-dev] Two warnings with clang 3.5 on ppc63le</span><o:p></o:p></p>
<div class="MsoNormal">
<hr size="2" width="100%" noshade="" style="color:#8091A5" align="left">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<br>
<tt><span style="font-size:10.0pt">> If you'd like to prevent this, you'll need to change the type of the variable to int
</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>> (or unsigned int, etc.). You might notice that in LLVM, for example, we have many 'enum'
</tt><br>
<tt>> variables that are typed as 'int' or 'unsigned' for a similar reason (if you want to use
</tt><br>
<tt>> an enum to name some possible integer values, but allow others, you can't actually use an
</tt><br>
<tt>> enum as the variable type).</tt><br>
<br>
<tt>So the right answer, then, would be to change the formal argument of the function to be of
</tt><br>
<tt>type "int", rather than the enum type, and rely on the fact that enums are silently, automatically, cast</tt><br>
<tt>to int.</tt><br>
<br>
<tt>-- Jim</tt><br>
<br>
<tt>James Cownie <<a href="mailto:james.h.cownie@intel.com">james.h.cownie@intel.com</a>></tt><br>
<tt>SSG/DPD/TCAR (Technical Computing, Analyzers and Runtimes)</tt><br>
<tt>Tel: +44 117 9071438</tt><br>
<br>
<tt>-----Original Message-----</tt><br>
<tt>From: Hal Finkel [<a href="mailto:hfinkel@anl.gov">mailto:hfinkel@anl.gov</a>]
</tt><br>
<tt>Sent: Monday, March 2, 2015 11:15 AM</tt><br>
<tt>To: Cownie, James H</tt><br>
<tt>Cc: Carlo Bertolli; <a href="mailto:openmp-dev@dcs-maillist2.engr.illinois.edu">
openmp-dev@dcs-maillist2.engr.illinois.edu</a></tt><br>
<tt>Subject: Re: [Openmp-dev] Two warnings with clang 3.5 on ppc63le</tt><br>
<br>
<tt>----- Original Message -----</tt><br>
<tt>> From: "James H Cownie" <<a href="mailto:james.h.cownie@intel.com">james.h.cownie@intel.com</a>></tt><br>
<tt>> To: "Carlo Bertolli" <<a href="mailto:cbertol@us.ibm.com">cbertol@us.ibm.com</a>>,
<a href="mailto:openmp-dev@dcs-maillist2.engr.illinois.edu">openmp-dev@dcs-maillist2.engr.illinois.edu</a></tt><br>
<tt>> Sent: Monday, March 2, 2015 4:28:27 AM</tt><br>
<tt>> Subject: Re: [Openmp-dev] Two warnings with clang 3.5 on ppc63le</tt><br>
<tt>> </tt><br>
<tt>> 1.</tt><br>
<tt>> /home/compteam/slave0/build_folder_omp/libiomp-src/runtime/src/kmp_error.c:124:23:</tt><br>
<tt>> warning: comparison of constant 16 with expression of type 'enum</tt><br>
<tt>> cons_type' is always true</tt><br>
<tt>> [-Wtautological-constant-out-of-range-compare]</tt><br>
<tt>> if ( 0 < ct && ct <= cons_text_c_num ) {;</tt><br>
<tt>> ~~ ^ ~~~~~~~~~~~~~~~</tt><br>
<tt>> </tt><br>
<tt>> It looks like that there are no machines where const char * is more</tt><br>
<tt>> that 64-bit. The second check can be removed safely - maybe the</tt><br>
<tt>> author of this intended something different?</tt><br>
<tt>> </tt><br>
<tt>> I think you’re misunderstanding the point here. cons_text_c_num gives</tt><br>
<tt>> us the number of elements in the table. The point so to ensure that</tt><br>
<tt>> the value we’ve been passed is a correct index into the table. The</tt><br>
<tt>> compiler is right that * if * the value passed is a correct member</tt><br>
<tt>> of the enumeration it can’t be outside the range, but the check is</tt><br>
<tt>> there precisely to ensure that the value passed in is in range</tt><br>
<tt>> (because we can’t tell here that someone didn’t call this with</tt><br>
<tt>> “(enum cons_type)1000”).</tt><br>
<tt>> </tt><br>
<tt>> So I think what we need here is a cast so that your compiler is</tt><br>
<tt>> happy</tt><br>
<br>
<tt>To be clear, the problem with the happiness of the compiler here is that, as written, the compiler is free to remove the check all together. Adding the cast may silence the warning, but the compiler's optimizer is still free to infer the range of the variable
based on its original type. If you'd like to prevent this, you'll need to change the type of the variable to int (or unsigned int, etc.). You might notice that in LLVM, for example, we have many 'enum' variables that are typed as 'int' or 'unsigned' for a
similar reason (if you want to use an enum to name some possible integer values, but allow others, you can't actually use an enum as the variable type).</tt><br>
<br>
<tt>-Hal</tt><br>
<br>
<tt>>, rather than removing the test.</tt><br>
<tt>> </tt><br>
<tt>> Something like</tt><br>
<tt>> </tt><br>
<tt>> if ( 0 < ct && ((int)ct) <= cons_text_c_num ) {;</tt><br>
<tt>> </tt><br>
<tt>> You could write the whole thing as</tt><br>
<tt>> </tt><br>
<tt>> if ( ((unsigned int)ct) <= cons_text_c_num ) {;</tt><br>
<tt>> but that may be a little too clever for its own good, especially</tt><br>
<tt>> since the performance of this code can’t matter.</tt><br>
<tt>> </tt><br>
<tt>> -- Jim</tt><br>
<tt>> </tt><br>
<tt>> James Cownie <<a href="mailto:james.h.cownie@intel.com">james.h.cownie@intel.com</a>></tt><br>
<tt>> SSG/DPD/TCAR (Technical Computing, Analyzers and Runtimes)</tt><br>
<tt>> </tt><br>
<tt>> Tel: +44 117 9071438</tt><br>
<tt>> </tt><br>
<tt>> </tt><br>
<tt>> </tt><br>
<tt>> </tt><br>
<tt>> </tt><br>
<tt>> From: <a href="mailto:openmp-dev-bounces@cs.uiuc.edu">openmp-dev-bounces@cs.uiuc.edu</a></tt><br>
<tt>> [<a href="mailto:openmp-dev-bounces@cs.uiuc.edu">mailto:openmp-dev-bounces@cs.uiuc.edu</a>] On Behalf Of Carlo Bertolli</tt><br>
<tt>> Sent: Friday, February 27, 2015 10:57 PM</tt><br>
<tt>> To: <a href="mailto:openmp-dev@dcs-maillist2.engr.illinois.edu">openmp-dev@dcs-maillist2.engr.illinois.edu</a></tt><br>
<tt>> Subject: [Openmp-dev] Two warnings with clang 3.5 on ppc63le</tt><br>
<tt>> </tt><br>
<tt>> </tt><br>
<tt>> </tt><br>
<tt>> Hi</tt><br>
<tt>> </tt><br>
<tt>> Using clang 3.5 on ppc64le, I obtained the following warnings.</tt><br>
<tt>> </tt><br>
<tt>> 1.</tt><br>
<tt>> /home/compteam/slave0/build_folder_omp/libiomp-src/runtime/src/kmp_error.c:124:23:</tt><br>
<tt>> warning: comparison of constant 16 with expression of type 'enum</tt><br>
<tt>> cons_type' is always true</tt><br>
<tt>> [-Wtautological-constant-out-of-range-compare]</tt><br>
<tt>> if ( 0 < ct && ct <= cons_text_c_num ) {;</tt><br>
<tt>> ~~ ^ ~~~~~~~~~~~~~~~</tt><br>
<tt>> </tt><br>
<tt>> It looks like that there are no machines where const char * is more</tt><br>
<tt>> that 64-bit. The second check can be removed safely - maybe the</tt><br>
<tt>> author of this intended something different?</tt><br>
<tt>> </tt><br>
<tt>> 2.</tt><br>
<tt>> /home/compteam/slave0/build_folder_omp/libiomp-src/runtime/src/kmp_runtime.c:270:58:</tt><br>
<tt>> warning: multiple unsequenced modifications to 'gtid'</tt><br>
<tt>> [-Wunsequenced]</tt><br>
<tt>> if ( __kmp_env_checks == TRUE && !KMP_UBER_GTID(gtid =</tt><br>
<tt>> __kmp_gtid_from_thread( th )))</tt><br>
<tt>> ^</tt><br>
<tt>> /home/compteam/slave0/build_folder_omp/libiomp-src/runtime/src/kmp.h:958:25:</tt><br>
<tt>> note: expanded from macro 'KMP_UBER_GTID'</tt><br>
<tt>> (__kmp_threads[(gtid)] == __kmp_root[(gtid)]->r.r_uber_thread)\</tt><br>
<tt>> ^</tt><br>
<tt>> </tt><br>
<tt>> gtid here is modified multiple times. We can just move the assignment</tt><br>
<tt>> out of the if and have only gtid as parameter of the macro.</tt><br>
<tt>> </tt><br>
<tt>> </tt><br>
<tt>> Below a patch that fixes these problems. Please let me know your</tt><br>
<tt>> thoughts on this.</tt><br>
<tt>> </tt><br>
<tt>> Thanks</tt><br>
<tt>> </tt><br>
<tt>> -- Carlo</tt><br>
<tt>> </tt><br>
<tt>> </tt><br>
<tt>> </tt><br>
<tt>> </tt><br>
<tt>> diff --git a/runtime/src/kmp_error.c b/runtime/src/kmp_error.c</tt><br>
<tt>> index b76c109..4274365 100644</tt><br>
<tt>> --- a/runtime/src/kmp_error.c</tt><br>
<tt>> +++ b/runtime/src/kmp_error.c</tt><br>
<tt>> @@ -121,7 +121,7 @@ __kmp_pragma(</tt><br>
<tt>> kmp_str_buf_t buffer;</tt><br>
<tt>> kmp_msg_t prgm;</tt><br>
<tt>> __kmp_str_buf_init( & buffer );</tt><br>
<tt>> - if ( 0 < ct && ct <= cons_text_c_num ) {;</tt><br>
<tt>> + if ( 0 < ct ) {</tt><br>
<tt>> cons = cons_text_c[ ct ];</tt><br>
<tt>> } else {</tt><br>
<tt>> KMP_DEBUG_ASSERT( 0 );</tt><br>
<tt>> diff --git a/runtime/src/kmp_runtime.c b/runtime/src/kmp_runtime.c</tt><br>
<tt>> index 55b58ce..0a08993 100644</tt><br>
<tt>> --- a/runtime/src/kmp_runtime.c</tt><br>
<tt>> +++ b/runtime/src/kmp_runtime.c</tt><br>
<tt>> @@ -267,7 +267,8 @@ __kmp_check_stack_overlap( kmp_info_t *th )</tt><br>
<tt>> }</tt><br>
<tt>> </tt><br>
<tt>> /* No point in checking ubermaster threads since they use refinement</tt><br>
<tt>> and cannot overlap */</tt><br>
<tt>> - if ( __kmp_env_checks == TRUE && !KMP_UBER_GTID(gtid =</tt><br>
<tt>> __kmp_gtid_from_thread( th )))</tt><br>
<tt>> + gtid = __kmp_gtid_from_thread( th );</tt><br>
<tt>> + if ( __kmp_env_checks == TRUE && !KMP_UBER_GTID(gtid))</tt><br>
<tt>> {</tt><br>
<tt>> KA_TRACE(10,("__kmp_check_stack_overlap: performing extensive</tt><br>
<tt>> checking\n"));</tt><br>
<tt>> if ( stack_beg == NULL ) {</tt><br>
<tt>> </tt><br>
<tt>> ---------------------------------------------------------------------</tt><br>
<tt>> Intel Corporation (UK) Limited</tt><br>
<tt>> Registered No. 1134945 (England)</tt><br>
<tt>> Registered Office: Pipers Way, Swindon SN3 1RJ</tt><br>
<tt>> VAT No: 860 2173 47</tt><br>
<tt>> </tt><br>
<tt>> This e-mail and any attachments may contain confidential material for</tt><br>
<tt>> the sole use of the intended recipient(s). Any review or distribution</tt><br>
<tt>> by others is strictly prohibited. If you are not the intended</tt><br>
<tt>> recipient, please contact the sender and delete all copies.</tt><br>
<tt>> _______________________________________________</tt><br>
<tt>> Openmp-dev mailing list</tt><br>
<tt>> <a href="mailto:Openmp-dev@dcs-maillist2.engr.illinois.edu">Openmp-dev@dcs-maillist2.engr.illinois.edu</a></tt><br>
<tt>> <a href="http://lists.cs.uiuc.edu/mailman/listinfo/openmp-dev">http://lists.cs.uiuc.edu/mailman/listinfo/openmp-dev</a></tt><br>
<tt>> </tt><br>
<br>
<tt>-- </tt><br>
<tt>Hal Finkel</tt><br>
<tt>Assistant Computational Scientist</tt><br>
<tt>Leadership Computing Facility</tt><br>
<tt>Argonne National Laboratory</tt><br>
<tt>---------------------------------------------------------------------</tt><br>
<tt>Intel Corporation (UK) Limited</tt><br>
<tt>Registered No. 1134945 (England)</tt><br>
<tt>Registered Office: Pipers Way, Swindon SN3 1RJ</tt><br>
<tt>VAT No: 860 2173 47</tt><br>
<br>
<tt>This e-mail and any attachments may contain confidential material for</tt><br>
<tt>the sole use of the intended recipient(s). Any review or distribution</tt><br>
<tt>by others is strictly prohibited. If you are not the intended</tt><br>
<tt>recipient, please contact the sender and delete all copies.</tt></span><o:p></o:p></p>
</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>