<html>
<head>
<base href="http://llvm.org/bugs/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - clang should support Annex F of ISO C (IEC 60559 / IEEE 754)"
href="http://llvm.org/bugs/show_bug.cgi?id=17005">17005</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>clang should support Annex F of ISO C (IEC 60559 / IEEE 754)
</td>
</tr>
<tr>
<th>Product</th>
<td>clang
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>-New Bugs
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedclangbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>vincent-llvm@vinc17.net
</td>
</tr>
<tr>
<th>CC</th>
<td>llvmbugs@cs.uiuc.edu
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr></table>
<p>
<div>
<pre>clang should support Annex F of ISO C (IEC 60559 / IEEE 754), at least the
basic features. Support could be controlled by options; for instance, it could
be disabled by options like GCC's -ffast-math.
If clang intends to be a replacement for GCC (as its Wikipedia page says), this
is really a must. GCC's IEEE 754 support is rather good, though not complete:
<a href="http://gcc.gnu.org/wiki/FloatingPointMath">http://gcc.gnu.org/wiki/FloatingPointMath</a>
And clang should be at least as good as GCC. Currently clang doesn't even
support basic features such as division by zero, which is regarded as undefined
(as said in <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED MOVED - clang sanitizer regards IEC 60559 floating-point division by zero as undefined"
href="show_bug.cgi?id=17000">bug 17000</a>).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>