This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug testsuite/21910] Files from previous runs can make some testcases fail
- From: "e9925248 at stud4 dot tuwien dot ac dot at" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 5 Jun 2005 13:01:23 -0000
- Subject: [Bug testsuite/21910] Files from previous runs can make some testcases fail
- References: <20050604104619.21910.e9925248@stud4.tuwien.ac.at>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From e9925248 at stud4 dot tuwien dot ac dot at 2005-06-05 13:01 -------
The example was taken out of a test log created at the beginning of May. The
current log where simliar failures for a lot files occured was not available any
more, because I had overwritten it with a new run, after deleting the files
causing the errors to verify the solution.
To problem is, that the testsuite searches for pattern XXXX.t??.XXX, if it wants
to open a dump file, and try to open the result. If multiple files match this
pattern, such an error occurs (see lib/scantree.exp).
To reproduce it on a clean directory, create a file named ssa-sink-1.c.t46.sink
(such a file was created some time ago by a testsuite run, because some error
occured while checking this testcase) in the testsuite run directory (where
gcc.sum is put). A make check prints then the following error:
ERROR: gcc.dg/tree-ssa/ssa-sink-1.c: error executing dg-final: couldn't open
"ssa-sink-1.c.t46.sink ssa-sink-1.c.t52.sink": no such file or directory
It leaves additionally ssa-sink-1.c.t52.sink in the directory. If the number of
the sink pass would change again, a third file would appear in the error message.
I know, this is not a severe error, as a rm -f testsuite/*.c.t* before each make
check solves the problem.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21910