<html>
<head>
<base href="https://llvm.org/bugs/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:rnk@google.com" title="Reid Kleckner <rnk@google.com>"> <span class="fn">Reid Kleckner</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED INVALID - fatal error in backend for g++.dg/other/pr59492.C"
href="https://llvm.org/bugs/show_bug.cgi?id=22917">bug 22917</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>REOPENED
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>rnk@google.com
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>INVALID
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED INVALID - fatal error in backend for g++.dg/other/pr59492.C"
href="https://llvm.org/bugs/show_bug.cgi?id=22917#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED INVALID - fatal error in backend for g++.dg/other/pr59492.C"
href="https://llvm.org/bugs/show_bug.cgi?id=22917">bug 22917</a>
from <span class="vcard"><a class="email" href="mailto:rnk@google.com" title="Reid Kleckner <rnk@google.com>"> <span class="fn">Reid Kleckner</span></a>
</span></b>
<pre>The __builtin_* intrinsics aren't really the public user interface for this
functionality. The intrinsics documented by Intel provided by the *mmintrin.h
headers are the public facing interface. If you include immintrin.h and use
_rdrand32_step() without -march=ivybridge or better, you'll get an undeclared
id error from the frontend. This is a bad diagnostic and we could do better,
but this is a much broader issue that affects all conditionally supported
intrinsics provided by immintrin.h.
Also, passing 100% of the GCC test suite is not a goal of the Clang project.
People have looked into passing it before, and the consensus is that the
remaining failures are not worth fixing because they don't help us compile more
real world code.</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>