This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
simple question about testresults list
- To: gcc at gcc dot gnu dot org
- Subject: simple question about testresults list
- From: Vincent Diepeveen <diep at xs4all dot nl>
- Date: Sat, 10 Feb 2001 06:02:59 +0100
Hello, how to read the below testresults in
the testresults list, as i don't understand the
whole line at all, are there .c files that by
accident carries a date less as a month ago?
Also nearly all optimization flags it fails
upon this .c file: 20010113-1.c
How bad is it to fail like that on this file,
is the .c file simply wrong?
------------------------------------------
Native configuration is i686-pc-linux-gnu
=== gcc tests ===
Running target unix/-fPIC
FAIL: gcc.c-torture/compile/20010113-1.c, -O0
FAIL: gcc.c-torture/compile/20010113-1.c, -O1
FAIL: gcc.c-torture/compile/20010113-1.c, -O2
FAIL: gcc.c-torture/compile/20010113-1.c, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/compile/20010113-1.c, -O3 -g
FAIL: gcc.c-torture/compile/20010113-1.c, -Os
FAIL: gcc.c-torture/compile/20001226-1.c, -O1
FAIL: gcc.c-torture/compile/20001226-1.c, -O2
FAIL: gcc.c-torture/compile/20001226-1.c, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/compile/20001226-1.c, -O3 -g
FAIL: gcc.c-torture/compile/20001226-1.c, -Os
FAIL: gcc.c-torture/compile/20000804-1.c, -O0
FAIL: gcc.c-torture/execute/20010114-2.c execution, -O1
FAIL: gcc.c-torture/execute/20010114-2.c execution, -O2