<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Sorry I lost track of this email thread. I got caught up with
other things. I'm wondering whether you have tried compiling with
fp-precise? I'm just wondering whether it could be a problem with
Intel's optimization.<br>
</p>
<p>--Steve<br>
</p>
<div class="moz-cite-prefix">On 9/1/2021 6:21 AM, Hee Il Kim wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAODOiE5365+pVmXWHDz+NXgoq6dc--5Q8U4Mzy=UwWMs=J81Vg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">
<div>Hi,</div>
<div><br>
</div>
<div>As James Healy mentioned in the post "[Users] Einstein
Toolkit and modern AMD supercomputer", I found
static_tov.par passed the test for the Intel issue. So some
bns-generic codes would make NaNs. But less probable because
the only bns-generic code would be NSTracker but I've
already encountered the NaN production issue w/wo NSTracker.</div>
<div><br>
</div>
<div>NaNChecker itself could be suspected but both bns and
tove tests are using NaNChecker.</div>
<div><br>
</div>
<div>Rather, it could be a generic issue of Intel compiler.
There are some bugs reported and new features in handling
NaNs for the case of ifx. Those look just irrelevant yet.</div>
<div><br>
</div>
<div>Hee Il </div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@einsteintoolkit.org">Users@einsteintoolkit.org</a>
<a class="moz-txt-link-freetext" href="http://lists.einsteintoolkit.org/mailman/listinfo/users">http://lists.einsteintoolkit.org/mailman/listinfo/users</a>
</pre>
</blockquote>
</body>
</html>