llvm-project/clang/test/VFS/include-virtual-from-real.c

// RUN: rm -rf %t
// RUN: mkdir -p %t
// RUN: echo '#include "not_real.h"' > %t/include_not_real.h
// RUN: sed -e "s@INPUT_DIR@%{/S:regex_replacement}/Inputs@g" -e "s@OUT_DIR@%{/t:regex_replacement}@g" %S/Inputs/vfsoverlay.yaml > %t.yaml
// RUN: %clang_cc1 -Werror -ivfsoverlay %t.yaml -I %t -fsyntax-only %s

#include "include_not_real.h"

void foo(void) {
  bar();
}
Add a driver option -ivfsoverlay Reads the description of a virtual filesystem from a file and overlays it over the real file system. llvm-svn: 202176 2014-02-25 18:23:47 +00:00			`// RUN: rm -rf %t`
			`// RUN: mkdir -p %t`
			`// RUN: echo '#include "not_real.h"' > %t/include_not_real.h`
Fix `sed -e s@FOO@%/S@` and similar when there's @'s in the working directory Jenkins sometimes starts a new working directory by appending @2 (or incrementing the number if the @n suffix is already there). This causes several clang tests to fail as: s@INPUT_DIR@%/S/Inputs@g gets expanded to the invalid: s@INPUT_DIR@/path/to/workdir@2/Inputs@g ~~~~~~~~~~ where the part marked with ~'s is interpreted as the flags. These are invalid and the test fails. Previous fixes simply exchanged the @ character for another like \| but that's just moving the problem. Address it by adding an expansion that escapes the @ character we're using as a delimiter as well as other magic characters in the replacement of sed's s@@@. There's still room for expansions to cause trouble though. One I ran into while testing this was that having a directory called foo@bar causes lots of `CHECK-NOT: foo` directives to match. There's also things like directories containing `\1` 2019-12-03 15:22:30 -08:00			`// RUN: sed -e "s@INPUT_DIR@%{/S:regex_replacement}/Inputs@g" -e "s@OUT_DIR@%{/t:regex_replacement}@g" %S/Inputs/vfsoverlay.yaml > %t.yaml`
Add a driver option -ivfsoverlay Reads the description of a virtual filesystem from a file and overlays it over the real file system. llvm-svn: 202176 2014-02-25 18:23:47 +00:00			`// RUN: %clang_cc1 -Werror -ivfsoverlay %t.yaml -I %t -fsyntax-only %s`
Start porting ivfsoverlay tests to Windows Part of PR43272, the changes are: 1. Use @ as the sed pattern delimiter instead of : so that the drive letter in lit substitutions isn't an issue. 2. Use the %/t and %/S substitutions to get paths with forward slashes to work around string quoting issues in the yaml file. 3. Replace REQUIRES:shell with XFAIL:windows. These tests should pass on Windows, but do not for reasons that are not yet understood. We would like to know if they pass unexpectedly. I was able to remove the XFAILs from two tests, since they already pass with my sed fix: clang/test/VFS/module_missing_vfs.m clang/test/VFS/test_nonmodular.c Reviewers: amccarth Differential Revision: https://reviews.llvm.org/D67454 llvm-svn: 371663 2019-09-11 20:56:25 +00:00
Add a driver option -ivfsoverlay Reads the description of a virtual filesystem from a file and overlays it over the real file system. llvm-svn: 202176 2014-02-25 18:23:47 +00:00			`#include "include_not_real.h"`

Use functions with prototypes when appropriate; NFC A significant number of our tests in C accidentally use functions without prototypes. This patch converts the function signatures to have a prototype for the situations where the test is not specific to K&R C declarations. e.g., void func(); becomes void func(void); This is the eighth batch of tests being updated (there are a significant number of other tests left to be updated). 2022-02-12 07:23:43 -05:00			`void foo(void) {`
Add a driver option -ivfsoverlay Reads the description of a virtual filesystem from a file and overlays it over the real file system. llvm-svn: 202176 2014-02-25 18:23:47 +00:00			`bar();`
			`}`