#include <VerifyDiagnosticConsumer.h>

Inheritance diagram for clang::VerifyDiagnosticConsumer:

Collaboration diagram for clang::VerifyDiagnosticConsumer:

Classes
class	Directive
struct	ExpectedData
class	UnparsedFileStatus
Public Types
enum	DirectiveStatus { HasNoDirectives, HasNoDirectivesReported, HasExpectedNoDiagnostics, HasOtherExpectedDirectives }
enum	ParsedStatus { IsParsed, IsUnparsed, IsUnparsedNoDirectives }
typedef std::vector < std::unique_ptr< Directive > >	DirectiveList
Public Member Functions
	VerifyDiagnosticConsumer (DiagnosticsEngine &Diags)
	~VerifyDiagnosticConsumer ()
void	BeginSourceFile (const LangOptions &LangOpts, const Preprocessor *PP) override
	Callback to inform the diagnostic client that processing of a source file is beginning.
void	EndSourceFile () override
	Callback to inform the diagnostic client that processing of a source file has ended.
void	UpdateParsedFileStatus (SourceManager &SM, FileID FID, ParsedStatus PS)
	Update lists of parsed and unparsed files.
bool	HandleComment (Preprocessor &PP, SourceRange Comment) override
void	HandleDiagnostic (DiagnosticsEngine::Level DiagLevel, const Diagnostic &Info) override
	Handle this diagnostic, reporting it to the user or capturing it to a log as needed.

Detailed Description

VerifyDiagnosticConsumer - Create a diagnostic client which will use markers in the input source to check that all the emitted diagnostics match those expected.

USING THE DIAGNOSTIC CHECKER:

Indicating that a line expects an error or a warning is simple. Put a comment on the line that has the diagnostic, use:

   expected-{error,warning,remark,note}

to tag if it's an expected error, remark or warning, and place the expected text between {{ and }} markers. The full text doesn't have to be included, only enough to ensure that the correct diagnostic was emitted.

Here's an example:

   int A = B; // expected-error {{use of undeclared identifier 'B'}}

You can place as many diagnostics on one line as you wish. To make the code more readable, you can use slash-newline to separate out the diagnostics.

Alternatively, it is possible to specify the line on which the diagnostic should appear by appending "@<line>" to "expected-<type>", for example:

   #warning some text
   // expected-warning@10 {{some text}}

The line number may be absolute (as above), or relative to the current line by prefixing the number with either '+' or '-'.

If the diagnostic is generated in a separate file, for example in a shared header file, it may be beneficial to be able to declare the file in which the diagnostic will appear, rather than placing the expected-* directive in the actual file itself. This can be done using the following syntax:

   // expected-error@path/include.h:15 {{error message}}

The path can be absolute or relative and the same search paths will be used as for #include directives. The line number in an external file may be substituted with '*' meaning that any line number will match (useful where the included file is, for example, a system header where the actual line number may change and is not critical).

The simple syntax above allows each specification to match exactly one error. You can use the extended syntax to customize this. The extended syntax is "expected-<type> <n> {{diag text}}", where <type> is one of "error", "warning" or "note", and <n> is a positive integer. This allows the diagnostic to appear as many times as specified. Example:

   void f(); // expected-note 2 {{previous declaration is here}}

Where the diagnostic is expected to occur a minimum number of times, this can be specified by appending a '+' to the number. Example:

   void f(); // expected-note 0+ {{previous declaration is here}}
   void g(); // expected-note 1+ {{previous declaration is here}}

In the first example, the diagnostic becomes optional, i.e. it will be swallowed if it occurs, but will not generate an error if it does not occur. In the second example, the diagnostic must occur at least once. As a short-hand, "one or more" can be specified simply by '+'. Example:

   void g(); // expected-note + {{previous declaration is here}}

A range can also be specified by "<n>-<m>". Example:

   void f(); // expected-note 0-1 {{previous declaration is here}}

In this example, the diagnostic may appear only once, if at all.

Regex matching mode may be selected by appending '-re' to type and including regexes wrapped in double curly braces in the directive, such as:

   expected-error-re {{format specifies type 'wchar_t **' (aka '{{.+}}')}}

Examples matching error: "variable has incomplete type 'struct s'"

   // expected-error {{variable has incomplete type 'struct s'}}
   // expected-error {{variable has incomplete type}}

   // expected-error-re {{variable has type 'struct {{.}}'}}
   // expected-error-re {{variable has type 'struct {{.*}}'}}
   // expected-error-re {{variable has type 'struct {{(.*)}}'}}
   // expected-error-re {{variable has type 'struct{{[[:space:]](.*)}}'}}

VerifyDiagnosticConsumer expects at least one expected-* directive to be found inside the source code. If no diagnostics are expected the following directive can be used to indicate this:

   // expected-no-diagnostics

Definition at line 141 of file VerifyDiagnosticConsumer.h.

Member Typedef Documentation

typedef std::vector<std::unique_ptr<Directive> > clang::VerifyDiagnosticConsumer::DirectiveList

Definition at line 187 of file VerifyDiagnosticConsumer.h.

Member Enumeration Documentation

enum clang::VerifyDiagnosticConsumer::DirectiveStatus

Enumerator:

HasNoDirectives
HasNoDirectivesReported
HasExpectedNoDiagnostics
HasOtherExpectedDirectives

Definition at line 205 of file VerifyDiagnosticConsumer.h.

enum clang::VerifyDiagnosticConsumer::ParsedStatus

Enumerator:

IsParsed	File has been processed via HandleComment.
IsUnparsed	File has diagnostics and may have directives.
IsUnparsedNoDirectives	File has diagnostics but guaranteed no directives.

Definition at line 256 of file VerifyDiagnosticConsumer.h.

Constructor & Destructor Documentation

VerifyDiagnosticConsumer::VerifyDiagnosticConsumer ( DiagnosticsEngine & Diags )

Create a new verifying diagnostic client, which will issue errors to the currently-attached diagnostic client when a diagnostic does not match what is expected (as indicated in the source file).

Definition at line 30 of file VerifyDiagnosticConsumer.cpp.

References clang::DiagnosticsEngine::getSourceManager(), and clang::DiagnosticsEngine::hasSourceManager().

VerifyDiagnosticConsumer::~VerifyDiagnosticConsumer ( )

Definition at line 41 of file VerifyDiagnosticConsumer.cpp.

References clang::DiagnosticsEngine::takeClient().

Member Function Documentation

void VerifyDiagnosticConsumer::BeginSourceFile	(	const LangOptions &	LangOpts,
		const Preprocessor *	PP
	)		`[override, virtual]`

Callback to inform the diagnostic client that processing of a source file is beginning.

Note that diagnostics may be emitted outside the processing of a source file, for example during the parsing of command line options. However, diagnostics with source range information are required to only be emitted in between BeginSourceFile() and EndSourceFile().

Parameters:

LangOpts	The language options for the source file being processed.
PP	The preprocessor object being used for the source; this is optional, e.g., it may not be present when processing AST source files.

Reimplemented from clang::DiagnosticConsumer.

Definition at line 73 of file VerifyDiagnosticConsumer.cpp.

References clang::DiagnosticConsumer::BeginSourceFile(), and clang::Preprocessor::getSourceManager().

void VerifyDiagnosticConsumer::EndSourceFile ( ) [override, virtual]

Callback to inform the diagnostic client that processing of a source file has ended.

The diagnostic client should assume that any objects made available via BeginSourceFile() are inaccessible.

Reimplemented from clang::DiagnosticConsumer.

Definition at line 94 of file VerifyDiagnosticConsumer.cpp.

References clang::DiagnosticConsumer::EndSourceFile().

bool VerifyDiagnosticConsumer::HandleComment	(	Preprocessor &	PP,
		SourceRange	Comment
	)		`[override, virtual]`

HandleComment - Hook into the preprocessor and extract comments containing expected errors and warnings.

Implements clang::CommentHandler.

Definition at line 522 of file VerifyDiagnosticConsumer.cpp.

References AttributeLangSupport::C, clang::SourceRange::getBegin(), clang::SourceManager::getCharacterData(), clang::SourceRange::getEnd(), clang::Preprocessor::getSourceManager(), ParseDirective(), and SM.

void VerifyDiagnosticConsumer::HandleDiagnostic	(	DiagnosticsEngine::Level	DiagLevel,
		const Diagnostic &	Info
	)		`[override, virtual]`

Handle this diagnostic, reporting it to the user or capturing it to a log as needed.

The default implementation just keeps track of the total number of warnings and errors.

Reimplemented from clang::DiagnosticConsumer.

Definition at line 110 of file VerifyDiagnosticConsumer.cpp.

References clang::HeaderSearch::findModuleForHeader(), clang::SourceManager::getExpansionLoc(), clang::SourceManager::getFileEntryForID(), clang::SourceManager::getFileID(), clang::Preprocessor::getHeaderSearchInfo(), clang::Diagnostic::getLocation(), clang::Diagnostic::getSourceManager(), clang::Diagnostic::hasSourceManager(), clang::SourceManager::isLoadedFileID(), IsUnparsed, IsUnparsedNoDirectives, clang::SourceLocation::isValid(), and UpdateParsedFileStatus().

void VerifyDiagnosticConsumer::UpdateParsedFileStatus	(	SourceManager &	SM,
		FileID	FID,
		ParsedStatus	PS
	)

Update lists of parsed and unparsed files.

Definition at line 767 of file VerifyDiagnosticConsumer.cpp.

References findDirectives(), clang::SourceManager::getFileEntryForID(), clang::FileID::isInvalid(), IsParsed, and IsUnparsedNoDirectives.

Referenced by HandleDiagnostic().

The documentation for this class was generated from the following files:

Classes

Public Types

Public Member Functions

Detailed Description

Member Typedef Documentation

Member Enumeration Documentation

Constructor & Destructor Documentation

Member Function Documentation