llvm-project/clang/test/Driver/analyze.c

// Verify that the analyzer gets the same flags as normal compilation
// (at least for a few key ones).

// RUN: env MACOSX_DEPLOYMENT_TARGET=10.5 clang -ccc-host-triple i386-apple-darwin9  -### --analyze -o /dev/null %s -msse 2> %t.log &&
// RUN: grep '"-analyze"' %t.log &&
// RUN: grep '"--fmath-errno=0"' %t.log &&
// RUN: grep '"-target-feature" "+sse"' %t.log &&
// RUN: grep '"-mmacosx-version-min=10.5"' %t.log
Make sure to pass the same options to the static analyzer as the compiler. - Code generation options may still affect the language... llvm-svn: 70393 2009-04-30 02:32:25 +08:00			`// Verify that the analyzer gets the same flags as normal compilation`
			`// (at least for a few key ones).`

Use env properly in test/Driver/analyze.c llvm-svn: 73609 2009-06-17 23:41:17 +08:00			`// RUN: env MACOSX_DEPLOYMENT_TARGET=10.5 clang -ccc-host-triple i386-apple-darwin9 -### --analyze -o /dev/null %s -msse 2> %t.log &&`
Make sure to pass the same options to the static analyzer as the compiler. - Code generation options may still affect the language... llvm-svn: 70393 2009-04-30 02:32:25 +08:00			`// RUN: grep '"-analyze"' %t.log &&`
			`// RUN: grep '"--fmath-errno=0"' %t.log &&`
Improve handling of (X86) target features. - This is a WIP... - This adds -march= handling to the driver, and fixes the defaulting of -mcpu on Darwin (which was using the wrong test). Instead of handling -m{sse, ...} in the driver, pass them to clang-cc as -target-feature [+-]name In clang-cc, communicate with the (clang) target to discover the legal features of a target, and the features which are enabled based on -mcpu. This is currently hardcoded just enough to not be a feature regression, we need to get this information from the backend's TableGen information somehow. This is used to construct the full list of features which are being used, which is in turn used to initialize the predefines. llvm-svn: 71061 2009-05-06 11:16:41 +08:00			`// RUN: grep '"-target-feature" "+sse"' %t.log &&`
Make these driver tests do the right thing even when MACOSX_DEPLOYMENT_TARGET is set. llvm-svn: 73583 2009-06-17 07:37:56 +08:00			`// RUN: grep '"-mmacosx-version-min=10.5"' %t.log`
Make sure to pass the same options to the static analyzer as the compiler. - Code generation options may still affect the language... llvm-svn: 70393 2009-04-30 02:32:25 +08:00