mirror of
git://gcc.gnu.org/git/gcc.git
synced 2025-03-23 04:20:27 +08:00
7fddf3dbb9
The outputs.exp tests check what temporary files are created and left behind with e.g. -save-temps. Additional files are created in presence of @file option. Adding an -I or -L option causes *another* temporary file to appear. I take it that's deliberate, as there are tests for that behavior. For native testing, the default test-framework baseboard file unix.exp doesn't add any -I or -L options and all tests pass. For a newlib target however, you'll have a couple of -L options (see the nopts handling in outputs.exp), leading to: Running /x/gcc/gcc/testsuite/gcc.misc-tests/outputs.exp ... FAIL: outputs exe savetmp namedb: extra outputs.args.1 FAIL: outputs exe savetmp named2: extra outputs.args.1 FAIL: outputs exe savetmp named2: extra outputs.args.3 FAIL: outputs lto sing unnamed: extra a.args.1 The failing tests are among the actual tests that check the behavior of @file, and are confused by the additional -L. Identify presence of -I or -L from the test framework and skip those tests. Tested cris-elf and x86_64-pc-linux-gnu. gcc/testsuite: * gcc.misc-tests/outputs.exp: Skip @file -save-temps tests if target test-framework has -L or -I options.
This directory contains the GNU Compiler Collection (GCC). The GNU Compiler Collection is free software. See the files whose names start with COPYING for copying permission. The manuals, and some of the runtime libraries, are under different terms; see the individual source files for details. The directory INSTALL contains copies of the installation information as HTML and plain text. The source of this information is gcc/doc/install.texi. The installation information includes details of what is included in the GCC sources and what files GCC installs. See the file gcc/doc/gcc.texi (together with other files that it includes) for usage and porting information. An online readable version of the manual is in the files gcc/doc/gcc.info*. See http://gcc.gnu.org/bugs/ for how to report bugs usefully. Copyright years on GCC source files may be listed using range notation, e.g., 1987-2012, indicating that every year in the range, inclusive, is a copyrightable year that could otherwise be listed individually.