llvm-project/clang/test/PCH/nonvisible-external-defs.c

// Test this without pch.
// RUN: %clang_cc1 -include %S/nonvisible-external-defs.h -fsyntax-only -verify %s

// Test with pch.
// RUN: %clang_cc1 -emit-pch -o %t %S/nonvisible-external-defs.h
// RUN: %clang_cc1 -include-pch %t -fsyntax-only -verify %s 

int g(int, float); // expected-error{{conflicting types}}

// expected-note@nonvisible-external-defs.h:10{{previous declaration}}
Support locally-declared external declarations in PCH files llvm-svn: 69833 2009-04-23 06:18:58 +08:00			`// Test this without pch.`
Update tests to use %clang_cc1 instead of 'clang-cc' or 'clang -cc1'. - This is designed to make it obvious that %clang_cc1 is a "test variable" which is substituted. It is '%clang_cc1' instead of '%clang -cc1' because it can be useful to redefine what gets run as 'clang -cc1' (for example, to set a default target). llvm-svn: 91446 2009-12-16 04:14:24 +08:00			`// RUN: %clang_cc1 -include %S/nonvisible-external-defs.h -fsyntax-only -verify %s`
Support locally-declared external declarations in PCH files llvm-svn: 69833 2009-04-23 06:18:58 +08:00
			`// Test with pch.`
Update tests to use %clang_cc1 instead of 'clang-cc' or 'clang -cc1'. - This is designed to make it obvious that %clang_cc1 is a "test variable" which is substituted. It is '%clang_cc1' instead of '%clang -cc1' because it can be useful to redefine what gets run as 'clang -cc1' (for example, to set a default target). llvm-svn: 91446 2009-12-16 04:14:24 +08:00			`// RUN: %clang_cc1 -emit-pch -o %t %S/nonvisible-external-defs.h`
			`// RUN: %clang_cc1 -include-pch %t -fsyntax-only -verify %s`
Support locally-declared external declarations in PCH files llvm-svn: 69833 2009-04-23 06:18:58 +08:00
			`int g(int, float); // expected-error{{conflicting types}}`

Extended VerifyDiagnosticConsumer to also verify source file for diagnostic. VerifyDiagnosticConsumer previously would not check that the diagnostic and its matching directive referenced the same source file. Common practice was to create directives that referenced other files but only by line number, and this led to problems such as when the file containing the directive didn't have enough lines to match the location of the diagnostic in the other file, leading to bizarre file formatting and other oddities. This patch causes VerifyDiagnosticConsumer to match source files as well as line numbers. Therefore, a new syntax is made available for directives, for example: // expected-error@file:line {{diagnostic message}} This extends the @line feature where "file" is the file where the diagnostic is generated. The @line syntax is still available and uses the current file for the diagnostic. "file" can be specified either as a relative or absolute path - although the latter has less usefulness, I think! The #include search paths will be used to locate the file and if it is not found an error will be generated. The new check is not optional: if the directive is in a different file to the diagnostic, the file must be specified. Therefore, a number of test-cases have been updated with regard to this. This closes out PR15613. llvm-svn: 179677 2013-04-17 16:06:46 +08:00			`// expected-note@nonvisible-external-defs.h:10{{previous declaration}}`