llvm-project/clang/test/Driver/cl-response-file.c

// Test that we use the Windows tokenizer for clang-cl response files. The
// trailing backslash before the space should be interpreted as a literal
// backslash. PR23709


// RUN: echo '/I%S\Inputs\cl-response-file\ /DFOO=2' > %t.rsp
// RUN: %clang_cl /c -### @%t.rsp -- %s 2>&1 | FileCheck %s

// CHECK: "-I" "{{.*}}\\Inputs\\cl-response-file\\" "-D" "FOO=2"
[clang-cl] Use the Windows response file tokenizer We were still using the Unix response file tokenizer for all driver modes. This was difficult to get right in the beginning because there is a circular dependency. The Driver class also can't officially determine its mode until it can see all possible --driver-mode= flags, and those flags could come from the response file. Now we use the Windows parsing algorithm if the program name looks like clang-cl, or if the --driver-mode=cl flag is present on the main command line. Fixes PR23709. Reviewers: hans Differential Revision: http://reviews.llvm.org/D11229 llvm-svn: 242346 2015-07-15 22:42:37 +00:00			`// Test that we use the Windows tokenizer for clang-cl response files. The`
			`// trailing backslash before the space should be interpreted as a literal`
			`// backslash. PR23709`



			`// RUN: echo '/I%S\Inputs\cl-response-file\ /DFOO=2' > %t.rsp`
			`// RUN: %clang_cl /c -### @%t.rsp -- %s 2>&1 \| FileCheck %s`

Use the AddAllArgs overload which accepts an ArrayRef of OptSpecifier. Differential Revision: http://reviews.llvm.org/D11599 llvm-svn: 243552 2015-07-29 18:39:14 +00:00			`// CHECK: "-I" "{{.*}}\\Inputs\\cl-response-file\\" "-D" "FOO=2"`