<html>
<head>
<base href="http://llvm.org/bugs/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:richard-llvm@metafoo.co.uk" title="Richard Smith <richard-llvm@metafoo.co.uk>"> <span class="fn">Richard Smith</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - False positive: Clang warns about unhanded switch values even if they are handled elsewhere"
href="http://llvm.org/bugs/show_bug.cgi?id=18392">bug 18392</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>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>richard-llvm@metafoo.co.uk
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>WONTFIX
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - False positive: Clang warns about unhanded switch values even if they are handled elsewhere"
href="http://llvm.org/bugs/show_bug.cgi?id=18392#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - False positive: Clang warns about unhanded switch values even if they are handled elsewhere"
href="http://llvm.org/bugs/show_bug.cgi?id=18392">bug 18392</a>
from <span class="vcard"><a class="email" href="mailto:richard-llvm@metafoo.co.uk" title="Richard Smith <richard-llvm@metafoo.co.uk>"> <span class="fn">Richard Smith</span></a>
</span></b>
<pre>Sorry, it's not feasible for us to fix this; this would require significant
flow analysis that is beyond the scope of what we want to do in the compiler
frontend. If you want this level of sophistication, the clang static analyzer
might work for you.
You can work around this with something like:
switch( value )
{
case AnEnumA: __builtin_unreachable(); // handled above
case AnEnumB: // ...</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>