<html>
<head>
<base href="http://llvm.org/bugs/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:dblaikie@gmail.com" title="David Blaikie <dblaikie@gmail.com>"> <span class="fn">David Blaikie</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED INVALID - Clang warnings are inconsistent between compiling from C source to object code and preprocessed C source to object code"
href="http://llvm.org/bugs/show_bug.cgi?id=21537">bug 21537</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>dblaikie@gmail.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 - Clang warnings are inconsistent between compiling from C source to object code and preprocessed C source to object code"
href="http://llvm.org/bugs/show_bug.cgi?id=21537#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED INVALID - Clang warnings are inconsistent between compiling from C source to object code and preprocessed C source to object code"
href="http://llvm.org/bugs/show_bug.cgi?id=21537">bug 21537</a>
from <span class="vcard"><a class="email" href="mailto:dblaikie@gmail.com" title="David Blaikie <dblaikie@gmail.com>"> <span class="fn">David Blaikie</span></a>
</span></b>
<pre>It is not the intention of the Clang project to produce the same diagnostics on
preprocessed and unpreprocessed source code.
If there's a particular diagnostic quality issue that might be addressed we can
look into it, but in some cases macro-ness is the best signal we have to remove
false positives and we might have to sacrifice some true positives for that
gain in signal/noise on a particular diagnostic.
If you have a particular need to take preprocessed code and compile it and get
the same result, you could consider using the -frewrite-includes mode that only
does #includes and leaves the macros in tact, this should generally produce
similar/identical diagnostics when compiled. (this can be used for distributed
build systems that need to send single input files to their build nodes)</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>