maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang/test/Driver/config-file3.c

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

105 lines
4.9 KiB
C
Raw Normal View History

Enable configuration files in clang Clang is inherently a cross compiler and can generate code for any target enabled during build. It however requires to specify many parameters in the invocation, which could be hardcoded during configuration process in the case of single-target compiler. The purpose of configuration files is to make specifying clang arguments easier. A configuration file is a collection of driver options, which are inserted into command line before other options specified in the clang invocation. It groups related options together and allows specifying them in simpler, more flexible and less error prone way than just listing the options somewhere in build scripts. Configuration file may be thought as a "macro" that names an option set and is expanded when the driver is called. Use of configuration files is described in `UserManual.rst`. Differential Revision: https://reviews.llvm.org/D24933 llvm-svn: 321621
2018-01-01 21:27:01 +08:00
// REQUIRES: shell
// REQUIRES: x86-registered-target
[test] Use %t instead of %T to remove race conditions between config-file3.c and target-override.c Both tests operate on `%T/testbin`. If the two tests run concurrently, one may fail. This is likely the root cause of flaky failures reported by https://lists.llvm.org/pipermail/llvm-dev/2020-September/144781.html https://llvm.org/docs/CommandGuide/lit.html says: `%T parent directory of %t (not unique, deprecated, do not use)` Reviewed By: dblaikie Differential Revision: https://reviews.llvm.org/D87103
2020-09-04 02:20:29 +08:00
// RUN: rm -rf %t && mkdir %t
Enable configuration files in clang Clang is inherently a cross compiler and can generate code for any target enabled during build. It however requires to specify many parameters in the invocation, which could be hardcoded during configuration process in the case of single-target compiler. The purpose of configuration files is to make specifying clang arguments easier. A configuration file is a collection of driver options, which are inserted into command line before other options specified in the clang invocation. It groups related options together and allows specifying them in simpler, more flexible and less error prone way than just listing the options somewhere in build scripts. Configuration file may be thought as a "macro" that names an option set and is expanded when the driver is called. Use of configuration files is described in `UserManual.rst`. Differential Revision: https://reviews.llvm.org/D24933 llvm-svn: 321621
2018-01-01 21:27:01 +08:00
//--- If config file is specified by relative path (workdir/cfg-s2), it is searched for by that path.
[test] Use %t instead of %T to remove race conditions between config-file3.c and target-override.c Both tests operate on `%T/testbin`. If the two tests run concurrently, one may fail. This is likely the root cause of flaky failures reported by https://lists.llvm.org/pipermail/llvm-dev/2020-September/144781.html https://llvm.org/docs/CommandGuide/lit.html says: `%T parent directory of %t (not unique, deprecated, do not use)` Reviewed By: dblaikie Differential Revision: https://reviews.llvm.org/D87103
2020-09-04 02:20:29 +08:00
// RUN: mkdir -p %t/workdir/subdir
// RUN: echo "@subdir/cfg-s2" > %t/workdir/cfg-1
// RUN: echo "-Wundefined-var-template" > %t/workdir/subdir/cfg-s2
Enable configuration files in clang Clang is inherently a cross compiler and can generate code for any target enabled during build. It however requires to specify many parameters in the invocation, which could be hardcoded during configuration process in the case of single-target compiler. The purpose of configuration files is to make specifying clang arguments easier. A configuration file is a collection of driver options, which are inserted into command line before other options specified in the clang invocation. It groups related options together and allows specifying them in simpler, more flexible and less error prone way than just listing the options somewhere in build scripts. Configuration file may be thought as a "macro" that names an option set and is expanded when the driver is called. Use of configuration files is described in `UserManual.rst`. Differential Revision: https://reviews.llvm.org/D24933 llvm-svn: 321621
2018-01-01 21:27:01 +08:00
//
[test] Use %t instead of %T to remove race conditions between config-file3.c and target-override.c Both tests operate on `%T/testbin`. If the two tests run concurrently, one may fail. This is likely the root cause of flaky failures reported by https://lists.llvm.org/pipermail/llvm-dev/2020-September/144781.html https://llvm.org/docs/CommandGuide/lit.html says: `%T parent directory of %t (not unique, deprecated, do not use)` Reviewed By: dblaikie Differential Revision: https://reviews.llvm.org/D87103
2020-09-04 02:20:29 +08:00
// RUN: ( cd %t && %clang --config workdir/cfg-1 -c %s -### 2>&1 | FileCheck %s -check-prefix CHECK-REL )
Enable configuration files in clang Clang is inherently a cross compiler and can generate code for any target enabled during build. It however requires to specify many parameters in the invocation, which could be hardcoded during configuration process in the case of single-target compiler. The purpose of configuration files is to make specifying clang arguments easier. A configuration file is a collection of driver options, which are inserted into command line before other options specified in the clang invocation. It groups related options together and allows specifying them in simpler, more flexible and less error prone way than just listing the options somewhere in build scripts. Configuration file may be thought as a "macro" that names an option set and is expanded when the driver is called. Use of configuration files is described in `UserManual.rst`. Differential Revision: https://reviews.llvm.org/D24933 llvm-svn: 321621
2018-01-01 21:27:01 +08:00
//
// CHECK-REL: Configuration file: {{.*}}/workdir/cfg-1
// CHECK-REL: -Wundefined-var-template
//--- Invocation qqq-clang-g++ tries to find config file qqq-clang-g++.cfg first.
//
[test] Use %t instead of %T to remove race conditions between config-file3.c and target-override.c Both tests operate on `%T/testbin`. If the two tests run concurrently, one may fail. This is likely the root cause of flaky failures reported by https://lists.llvm.org/pipermail/llvm-dev/2020-September/144781.html https://llvm.org/docs/CommandGuide/lit.html says: `%T parent directory of %t (not unique, deprecated, do not use)` Reviewed By: dblaikie Differential Revision: https://reviews.llvm.org/D87103
2020-09-04 02:20:29 +08:00
// RUN: mkdir %t/testdmode
// RUN: ln -s %clang %t/testdmode/qqq-clang-g++
// RUN: echo "-Wundefined-func-template" > %t/testdmode/qqq-clang-g++.cfg
// RUN: echo "-Werror" > %t/testdmode/qqq.cfg
// RUN: %t/testdmode/qqq-clang-g++ --config-system-dir= --config-user-dir= -c -no-canonical-prefixes %s -### 2>&1 | FileCheck %s -check-prefix FULL-NAME
Enable configuration files in clang Clang is inherently a cross compiler and can generate code for any target enabled during build. It however requires to specify many parameters in the invocation, which could be hardcoded during configuration process in the case of single-target compiler. The purpose of configuration files is to make specifying clang arguments easier. A configuration file is a collection of driver options, which are inserted into command line before other options specified in the clang invocation. It groups related options together and allows specifying them in simpler, more flexible and less error prone way than just listing the options somewhere in build scripts. Configuration file may be thought as a "macro" that names an option set and is expanded when the driver is called. Use of configuration files is described in `UserManual.rst`. Differential Revision: https://reviews.llvm.org/D24933 llvm-svn: 321621
2018-01-01 21:27:01 +08:00
//
// FULL-NAME: Configuration file: {{.*}}/testdmode/qqq-clang-g++.cfg
// FULL-NAME: -Wundefined-func-template
// FULL-NAME-NOT: -Werror
//
[Driver] Fix implicit config files from prefixed symlinks If -no-canonical-prefixes isn't used, the clang executable name used is the one of the actual executable, not the name of the symlink that the user invoked. In these cases, the target prefix was overridden based on the clang executable name. (On the other hand the implicit -target option that such a symlink adds, is added as an actual command line parameter in tools/driver/driver.cop, before resolving the symlink and finding the actual clang executable. Use the original ClangNameParts (set from argv[0] in tools/driver/driver.cpp) if it seems to be initialized propery. All existing tests of this feature used -no-canonical-prefixes (possibly because it also makes the driver look in the directory of the symlink instead of the directory of the executable); add another one that uses --config-user-dir= to specify the directory instead. (For actual users of such symlinks, outisde of the test suite, the directory is probably the same for both.) This makes this feature work more like what the documentation describes. Differential Revision: https://reviews.llvm.org/D45964 llvm-svn: 330871
2018-04-26 05:23:59 +08:00
//--- Invocation qqq-clang-g++ tries to find config file qqq-clang-g++.cfg even without -no-canonical-prefixes.
// (As the clang executable and symlink are in different directories, this
// requires specifying the path via --config-*-dir= though.)
//
[test] Use %t instead of %T to remove race conditions between config-file3.c and target-override.c Both tests operate on `%T/testbin`. If the two tests run concurrently, one may fail. This is likely the root cause of flaky failures reported by https://lists.llvm.org/pipermail/llvm-dev/2020-September/144781.html https://llvm.org/docs/CommandGuide/lit.html says: `%T parent directory of %t (not unique, deprecated, do not use)` Reviewed By: dblaikie Differential Revision: https://reviews.llvm.org/D87103
2020-09-04 02:20:29 +08:00
// RUN: %t/testdmode/qqq-clang-g++ --config-system-dir= --config-user-dir=%t/testdmode -c %s -### 2>&1 | FileCheck %s -check-prefix SYMLINK
[Driver] Fix implicit config files from prefixed symlinks If -no-canonical-prefixes isn't used, the clang executable name used is the one of the actual executable, not the name of the symlink that the user invoked. In these cases, the target prefix was overridden based on the clang executable name. (On the other hand the implicit -target option that such a symlink adds, is added as an actual command line parameter in tools/driver/driver.cop, before resolving the symlink and finding the actual clang executable. Use the original ClangNameParts (set from argv[0] in tools/driver/driver.cpp) if it seems to be initialized propery. All existing tests of this feature used -no-canonical-prefixes (possibly because it also makes the driver look in the directory of the symlink instead of the directory of the executable); add another one that uses --config-user-dir= to specify the directory instead. (For actual users of such symlinks, outisde of the test suite, the directory is probably the same for both.) This makes this feature work more like what the documentation describes. Differential Revision: https://reviews.llvm.org/D45964 llvm-svn: 330871
2018-04-26 05:23:59 +08:00
//
// SYMLINK: Configuration file: {{.*}}/testdmode/qqq-clang-g++.cfg
//
Enable configuration files in clang Clang is inherently a cross compiler and can generate code for any target enabled during build. It however requires to specify many parameters in the invocation, which could be hardcoded during configuration process in the case of single-target compiler. The purpose of configuration files is to make specifying clang arguments easier. A configuration file is a collection of driver options, which are inserted into command line before other options specified in the clang invocation. It groups related options together and allows specifying them in simpler, more flexible and less error prone way than just listing the options somewhere in build scripts. Configuration file may be thought as a "macro" that names an option set and is expanded when the driver is called. Use of configuration files is described in `UserManual.rst`. Differential Revision: https://reviews.llvm.org/D24933 llvm-svn: 321621
2018-01-01 21:27:01 +08:00
//--- File specified by --config overrides config inferred from clang executable.
//
[test] Use %t instead of %T to remove race conditions between config-file3.c and target-override.c Both tests operate on `%T/testbin`. If the two tests run concurrently, one may fail. This is likely the root cause of flaky failures reported by https://lists.llvm.org/pipermail/llvm-dev/2020-September/144781.html https://llvm.org/docs/CommandGuide/lit.html says: `%T parent directory of %t (not unique, deprecated, do not use)` Reviewed By: dblaikie Differential Revision: https://reviews.llvm.org/D87103
2020-09-04 02:20:29 +08:00
// RUN: %t/testdmode/qqq-clang-g++ --config-system-dir=%S/Inputs/config --config-user-dir= --config i386-qqq -c -no-canonical-prefixes %s -### 2>&1 | FileCheck %s -check-prefix CHECK-EXPLICIT
Enable configuration files in clang Clang is inherently a cross compiler and can generate code for any target enabled during build. It however requires to specify many parameters in the invocation, which could be hardcoded during configuration process in the case of single-target compiler. The purpose of configuration files is to make specifying clang arguments easier. A configuration file is a collection of driver options, which are inserted into command line before other options specified in the clang invocation. It groups related options together and allows specifying them in simpler, more flexible and less error prone way than just listing the options somewhere in build scripts. Configuration file may be thought as a "macro" that names an option set and is expanded when the driver is called. Use of configuration files is described in `UserManual.rst`. Differential Revision: https://reviews.llvm.org/D24933 llvm-svn: 321621
2018-01-01 21:27:01 +08:00
//
// CHECK-EXPLICIT: Configuration file: {{.*}}/Inputs/config/i386-qqq.cfg
//
//--- Invocation qqq-clang-g++ tries to find config file qqq.cfg if qqq-clang-g++.cfg is not found.
//
[test] Use %t instead of %T to remove race conditions between config-file3.c and target-override.c Both tests operate on `%T/testbin`. If the two tests run concurrently, one may fail. This is likely the root cause of flaky failures reported by https://lists.llvm.org/pipermail/llvm-dev/2020-September/144781.html https://llvm.org/docs/CommandGuide/lit.html says: `%T parent directory of %t (not unique, deprecated, do not use)` Reviewed By: dblaikie Differential Revision: https://reviews.llvm.org/D87103
2020-09-04 02:20:29 +08:00
// RUN: rm %t/testdmode/qqq-clang-g++.cfg
// RUN: %t/testdmode/qqq-clang-g++ --config-system-dir= --config-user-dir= -c -no-canonical-prefixes %s -### 2>&1 | FileCheck %s -check-prefix SHORT-NAME
Enable configuration files in clang Clang is inherently a cross compiler and can generate code for any target enabled during build. It however requires to specify many parameters in the invocation, which could be hardcoded during configuration process in the case of single-target compiler. The purpose of configuration files is to make specifying clang arguments easier. A configuration file is a collection of driver options, which are inserted into command line before other options specified in the clang invocation. It groups related options together and allows specifying them in simpler, more flexible and less error prone way than just listing the options somewhere in build scripts. Configuration file may be thought as a "macro" that names an option set and is expanded when the driver is called. Use of configuration files is described in `UserManual.rst`. Differential Revision: https://reviews.llvm.org/D24933 llvm-svn: 321621
2018-01-01 21:27:01 +08:00
//
// SHORT-NAME: Configuration file: {{.*}}/testdmode/qqq.cfg
// SHORT-NAME: -Werror
// SHORT-NAME-NOT: -Wundefined-func-template
//--- Config files are searched for in binary directory as well.
//
[test] Use %t instead of %T to remove race conditions between config-file3.c and target-override.c Both tests operate on `%T/testbin`. If the two tests run concurrently, one may fail. This is likely the root cause of flaky failures reported by https://lists.llvm.org/pipermail/llvm-dev/2020-September/144781.html https://llvm.org/docs/CommandGuide/lit.html says: `%T parent directory of %t (not unique, deprecated, do not use)` Reviewed By: dblaikie Differential Revision: https://reviews.llvm.org/D87103
2020-09-04 02:20:29 +08:00
// RUN: mkdir %t/testbin
// RUN: ln -s %clang %t/testbin/clang
// RUN: echo "-Werror" > %t/testbin/aaa.cfg
// RUN: %t/testbin/clang --config-system-dir= --config-user-dir= --config aaa.cfg -c -no-canonical-prefixes %s -### 2>&1 | FileCheck %s -check-prefix CHECK-BIN
Enable configuration files in clang Clang is inherently a cross compiler and can generate code for any target enabled during build. It however requires to specify many parameters in the invocation, which could be hardcoded during configuration process in the case of single-target compiler. The purpose of configuration files is to make specifying clang arguments easier. A configuration file is a collection of driver options, which are inserted into command line before other options specified in the clang invocation. It groups related options together and allows specifying them in simpler, more flexible and less error prone way than just listing the options somewhere in build scripts. Configuration file may be thought as a "macro" that names an option set and is expanded when the driver is called. Use of configuration files is described in `UserManual.rst`. Differential Revision: https://reviews.llvm.org/D24933 llvm-svn: 321621
2018-01-01 21:27:01 +08:00
//
// CHECK-BIN: Configuration file: {{.*}}/testbin/aaa.cfg
// CHECK-BIN: -Werror
//--- If command line contains options that change triple (for instance, -m32), clang tries
// reloading config file.
//--- When reloading config file, x86_64-clang-g++ tries to find config i386-clang-g++.cfg first.
//
[test] Use %t instead of %T to remove race conditions between config-file3.c and target-override.c Both tests operate on `%T/testbin`. If the two tests run concurrently, one may fail. This is likely the root cause of flaky failures reported by https://lists.llvm.org/pipermail/llvm-dev/2020-September/144781.html https://llvm.org/docs/CommandGuide/lit.html says: `%T parent directory of %t (not unique, deprecated, do not use)` Reviewed By: dblaikie Differential Revision: https://reviews.llvm.org/D87103
2020-09-04 02:20:29 +08:00
// RUN: mkdir %t/testreload
// RUN: ln -s %clang %t/testreload/x86_64-clang-g++
// RUN: echo "-Wundefined-func-template" > %t/testreload/i386-clang-g++.cfg
// RUN: echo "-Werror" > %t/testreload/i386.cfg
// RUN: %t/testreload/x86_64-clang-g++ --config-system-dir= --config-user-dir= -c -m32 -no-canonical-prefixes %s -### 2>&1 | FileCheck %s -check-prefix CHECK-RELOAD
Enable configuration files in clang Clang is inherently a cross compiler and can generate code for any target enabled during build. It however requires to specify many parameters in the invocation, which could be hardcoded during configuration process in the case of single-target compiler. The purpose of configuration files is to make specifying clang arguments easier. A configuration file is a collection of driver options, which are inserted into command line before other options specified in the clang invocation. It groups related options together and allows specifying them in simpler, more flexible and less error prone way than just listing the options somewhere in build scripts. Configuration file may be thought as a "macro" that names an option set and is expanded when the driver is called. Use of configuration files is described in `UserManual.rst`. Differential Revision: https://reviews.llvm.org/D24933 llvm-svn: 321621
2018-01-01 21:27:01 +08:00
//
// CHECK-RELOAD: Configuration file: {{.*}}/testreload/i386-clang-g++.cfg
// CHECK-RELOAD: -Wundefined-func-template
// CHECK-RELOAD-NOT: -Werror
//--- If config file is specified by --config and its name does not start with architecture, it is used without reloading.
//
[test] Use %t instead of %T to remove race conditions between config-file3.c and target-override.c Both tests operate on `%T/testbin`. If the two tests run concurrently, one may fail. This is likely the root cause of flaky failures reported by https://lists.llvm.org/pipermail/llvm-dev/2020-September/144781.html https://llvm.org/docs/CommandGuide/lit.html says: `%T parent directory of %t (not unique, deprecated, do not use)` Reviewed By: dblaikie Differential Revision: https://reviews.llvm.org/D87103
2020-09-04 02:20:29 +08:00
// RUN: %t/testreload/x86_64-clang-g++ --config-system-dir=%S/Inputs --config-user-dir= --config config-3 -c -m32 -no-canonical-prefixes %s -### 2>&1 | FileCheck %s -check-prefix CHECK-RELOAD1a
Enable configuration files in clang Clang is inherently a cross compiler and can generate code for any target enabled during build. It however requires to specify many parameters in the invocation, which could be hardcoded during configuration process in the case of single-target compiler. The purpose of configuration files is to make specifying clang arguments easier. A configuration file is a collection of driver options, which are inserted into command line before other options specified in the clang invocation. It groups related options together and allows specifying them in simpler, more flexible and less error prone way than just listing the options somewhere in build scripts. Configuration file may be thought as a "macro" that names an option set and is expanded when the driver is called. Use of configuration files is described in `UserManual.rst`. Differential Revision: https://reviews.llvm.org/D24933 llvm-svn: 321621
2018-01-01 21:27:01 +08:00
//
// CHECK-RELOAD1a: Configuration file: {{.*}}/Inputs/config-3.cfg
//
[test] Use %t instead of %T to remove race conditions between config-file3.c and target-override.c Both tests operate on `%T/testbin`. If the two tests run concurrently, one may fail. This is likely the root cause of flaky failures reported by https://lists.llvm.org/pipermail/llvm-dev/2020-September/144781.html https://llvm.org/docs/CommandGuide/lit.html says: `%T parent directory of %t (not unique, deprecated, do not use)` Reviewed By: dblaikie Differential Revision: https://reviews.llvm.org/D87103
2020-09-04 02:20:29 +08:00
// RUN: %t/testreload/x86_64-clang-g++ --config-system-dir=%S/Inputs --config-user-dir= --config config-3 -c -target i386 -no-canonical-prefixes %s -### 2>&1 | FileCheck %s -check-prefix CHECK-RELOAD1b
Enable configuration files in clang Clang is inherently a cross compiler and can generate code for any target enabled during build. It however requires to specify many parameters in the invocation, which could be hardcoded during configuration process in the case of single-target compiler. The purpose of configuration files is to make specifying clang arguments easier. A configuration file is a collection of driver options, which are inserted into command line before other options specified in the clang invocation. It groups related options together and allows specifying them in simpler, more flexible and less error prone way than just listing the options somewhere in build scripts. Configuration file may be thought as a "macro" that names an option set and is expanded when the driver is called. Use of configuration files is described in `UserManual.rst`. Differential Revision: https://reviews.llvm.org/D24933 llvm-svn: 321621
2018-01-01 21:27:01 +08:00
//
// CHECK-RELOAD1b: Configuration file: {{.*}}/Inputs/config-3.cfg
//--- If config file is specified by --config and its name starts with architecture, it is reloaded.
//
[test] Use %t instead of %T to remove race conditions between config-file3.c and target-override.c Both tests operate on `%T/testbin`. If the two tests run concurrently, one may fail. This is likely the root cause of flaky failures reported by https://lists.llvm.org/pipermail/llvm-dev/2020-September/144781.html https://llvm.org/docs/CommandGuide/lit.html says: `%T parent directory of %t (not unique, deprecated, do not use)` Reviewed By: dblaikie Differential Revision: https://reviews.llvm.org/D87103
2020-09-04 02:20:29 +08:00
// RUN: %t/testreload/x86_64-clang-g++ --config-system-dir=%S/Inputs/config --config-user-dir= --config x86_64-qqq -c -m32 -no-canonical-prefixes %s -### 2>&1 | FileCheck %s -check-prefix CHECK-RELOAD1c
Enable configuration files in clang Clang is inherently a cross compiler and can generate code for any target enabled during build. It however requires to specify many parameters in the invocation, which could be hardcoded during configuration process in the case of single-target compiler. The purpose of configuration files is to make specifying clang arguments easier. A configuration file is a collection of driver options, which are inserted into command line before other options specified in the clang invocation. It groups related options together and allows specifying them in simpler, more flexible and less error prone way than just listing the options somewhere in build scripts. Configuration file may be thought as a "macro" that names an option set and is expanded when the driver is called. Use of configuration files is described in `UserManual.rst`. Differential Revision: https://reviews.llvm.org/D24933 llvm-svn: 321621
2018-01-01 21:27:01 +08:00
//
// CHECK-RELOAD1c: Configuration file: {{.*}}/Inputs/config/i386-qqq.cfg
//--- x86_64-clang-g++ tries to find config i386.cfg if i386-clang-g++.cfg is not found.
//
[test] Use %t instead of %T to remove race conditions between config-file3.c and target-override.c Both tests operate on `%T/testbin`. If the two tests run concurrently, one may fail. This is likely the root cause of flaky failures reported by https://lists.llvm.org/pipermail/llvm-dev/2020-September/144781.html https://llvm.org/docs/CommandGuide/lit.html says: `%T parent directory of %t (not unique, deprecated, do not use)` Reviewed By: dblaikie Differential Revision: https://reviews.llvm.org/D87103
2020-09-04 02:20:29 +08:00
// RUN: rm %t/testreload/i386-clang-g++.cfg
// RUN: %t/testreload/x86_64-clang-g++ --config-system-dir= --config-user-dir= -c -m32 -no-canonical-prefixes %s -### 2>&1 | FileCheck %s -check-prefix CHECK-RELOAD1d
Enable configuration files in clang Clang is inherently a cross compiler and can generate code for any target enabled during build. It however requires to specify many parameters in the invocation, which could be hardcoded during configuration process in the case of single-target compiler. The purpose of configuration files is to make specifying clang arguments easier. A configuration file is a collection of driver options, which are inserted into command line before other options specified in the clang invocation. It groups related options together and allows specifying them in simpler, more flexible and less error prone way than just listing the options somewhere in build scripts. Configuration file may be thought as a "macro" that names an option set and is expanded when the driver is called. Use of configuration files is described in `UserManual.rst`. Differential Revision: https://reviews.llvm.org/D24933 llvm-svn: 321621
2018-01-01 21:27:01 +08:00
//
// CHECK-RELOAD1d: Configuration file: {{.*}}/testreload/i386.cfg
// CHECK-RELOAD1d: -Werror
// CHECK-RELOAD1d-NOT: -Wundefined-func-template