<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Undefined Behavior in JSValue cast from NaN"
href="https://bugs.webkit.org/show_bug.cgi?id=160322#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Undefined Behavior in JSValue cast from NaN"
href="https://bugs.webkit.org/show_bug.cgi?id=160322">bug 160322</a>
from <span class="vcard"><a class="email" href="mailto:jbedard@apple.com" title="Jonathan Bedard <jbedard@apple.com>"> <span class="fn">Jonathan Bedard</span></a>
</span></b>
<pre>It is possible that some compilers optimize out the double constructor. Open source clang (I specify open source because this bug was discovered with open source clang, not the version shipped with the operating system) almost certainly does not, otherwise this behavior would never have been caught in the first place. This is something I double check on.
I also agree with Kieth that in practice, the double constructor is not an issue, and can be ignored.
The question only question left, then, is whether the clarification of jsNaN() is worth it. I do think that regardless, this is probably worth a comment in the JSValue(double) constructor.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>