llvm-project/clang/test/Driver/cc-print-options.c

// RUN: env CC_PRINT_OPTIONS=1 \
// RUN:     CC_PRINT_OPTIONS_FILE=%t.log \
// RUN: %clang -no-canonical-prefixes -S -o %t.s %s
// RUN: FileCheck %s < %t.log

// CHECK: [Logging clang options]
// CHECK: {{.*}}clang{{.*}}"-S"
Driver: Support CC_PRINT_OPTIONS, used for logging the compile commands (in -v style) to a file. llvm-svn: 99054 2010-03-20 16:01:59 +08:00			`// RUN: env CC_PRINT_OPTIONS=1 \`
			`// RUN: CC_PRINT_OPTIONS_FILE=%t.log \`
Add -no-canonical-prefixes to tests which assert on the name of the built clang binary that is used by the test. Build systems that use symlinks for build outputs will fail these assertions otherwise. llvm-svn: 129482 2011-04-14 06:28:36 +08:00			`// RUN: %clang -no-canonical-prefixes -S -o %t.s %s`
Driver: Support CC_PRINT_OPTIONS, used for logging the compile commands (in -v style) to a file. llvm-svn: 99054 2010-03-20 16:01:59 +08:00			`// RUN: FileCheck %s < %t.log`

[PATCH] Reland [Clang] Un-break scan-build after integrated-cc1 change The issue was reported by @xazax.hun here: https://reviews.llvm.org/D69825#1827826 "This patch (D69825) breaks scan-build-py which parses the output of "-###" to get -cc1 command. There might be other tools with the same problems. Could we either remove (in-process) from CC1Command::Print or add a line break? Having the last line as a valid invocation is valuable and there might be tools relying on that." Differential Revision: https://reviews.llvm.org/D72982 2020-01-22 06:03:00 +08:00			`// CHECK: [Logging clang options]`
			`// CHECK: {{.}}clang{{.}}"-S"`
Driver: Support CC_PRINT_OPTIONS, used for logging the compile commands (in -v style) to a file. llvm-svn: 99054 2010-03-20 16:01:59 +08:00