Richard Smith 6d69fec645 Improve the diagnostic for #include_next occurring in a file not found
in the include path.

Instead of making the incorrect claim that the included file has an
absolute path, describe the actual problem: the including file was found
either by absolute path, or relative to such a file, or relative to the
primary source file.

llvm-svn: 356712
2019-03-21 20:42:13 +00:00

30 lines
819 B
C

// RUN: %clang_cc1 -verify %s -E -o /dev/null -I%S/Inputs/include-next-1 -I%S/Inputs/include-next-2 -DTEST=1
// RUN: %clang_cc1 -verify %s -E -o /dev/null -I%S/Inputs/include-next-1 -I%S/Inputs/include-next-2 -DTEST=2
// RUN: %clang_cc1 -verify %s -E -o /dev/null -I%S/Inputs/include-next-1 -I%S/Inputs/include-next-2 -DTEST=3
#if TEST == 1
// expected-warning@+1 {{#include_next in primary source file}}
#include_next "bar.h"
#if BAR != 1
#error wrong bar
#endif
#elif TEST == 2
// expected-no-diagnostics
#include "foo.h"
#if BAR != 2
#error wrong bar
#endif
#elif TEST == 3
// expected-warning@foo.h:1 {{#include_next in file found relative to primary source file or found by absolute path}}
#include "Inputs/include-next-1/foo.h"
#if BAR != 1
#error wrong bar
#endif
#undef BAR
#else
#error unknown test
#endif