summaryrefslogtreecommitdiffstats
path: root/clang/lib/Frontend/VerifyDiagnosticConsumer.cpp
Commit message (Collapse)AuthorAgeFilesLines
...
* <climits> has UINT_MAX, not <limits>.Eli Friedman2011-12-151-1/+1
| | | | llvm-svn: 146638
* Another fixit for r146633 (to make debian-fnt bot happy), try including ↵Anna Zaks2011-12-151-1/+1
| | | | | | limits instead. llvm-svn: 146637
* Fixit for r146633. Make sure UINT_MAX is defined on all platforms.Anna Zaks2011-12-151-0/+2
| | | | | | (Attempt to turn debian-fnt buildbot back to green.) llvm-svn: 146635
* Add support for matching one or more (aka regex +) diagnostic messages with ↵Anna Zaks2011-12-151-1/+14
| | | | | | | | | -verify. Ex: // expected-warning + {{tainted} llvm-svn: 146633
* Modify how the -verify flag works. Currently, the verification string andRichard Trieu2011-12-151-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | diagnostic message are compared. If either is a substring of the other, then no error is given. This gives rise to an unexpected case: // expect-error{{candidate function has different number of parameters}} will match the following error messages from Clang: candidate function has different number of parameters (expected 1 but has 2) candidate function has different number of parameters It will also match these other error messages: candidate function function has different number of parameters number of parameters This patch will change so that the verification string must be a substring of the diagnostic message before accepting. Also, all the failing tests from this change have been corrected. Some stats from this cleanup: 87 - removed extra spaces around verification strings 70 - wording updates to diagnostics 40 - extra leading or trailing characters (typos, unmatched parens or quotes) 35 - diagnostic level was included (error:, warning:, or note:) 18 - flag name put in the warning (-Wprotocol) llvm-svn: 146619
* Introduce a pure virtual clone() method to DiagnosticConsumer, so thatDouglas Gregor2011-09-291-0/+8
| | | | | | | | | we have the ability to create a new, distict diagnostic consumer when we go off and build a module. This avoids the currently horribleness where the same diagnostic consumer sees diagnostics for multiple translation units (and multiple SourceManagers!) causing all sorts of havok. llvm-svn: 140743
* Rename DiagnosticInfo to Diagnostic as per issue 5397David Blaikie2011-09-261-1/+1
| | | | llvm-svn: 140493
* Rename VerifyDiagnosticsClient to VerifyDiagnosticConsumer as per issue 5397David Blaikie2011-09-261-0/+533
llvm-svn: 140489
OpenPOWER on IntegriCloud