[LLVMbugs] [Bug 21537] Clang warnings are inconsistent between compiling from C source to object code and preprocessed C source to object code

[bugzilla-daemon at llvm.org]

http://llvm.org/bugs/show_bug.cgi?id=21537

David Blaikie <dblaikie at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |dblaikie at gmail.com
         Resolution|---                         |INVALID

--- Comment #1 from David Blaikie <dblaikie at gmail.com> ---
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)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20141111/778b9178/attachment.html>