This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

egcs-980321 on sparc-sun-solaris2.5.1 test results


--enable-{shared,haifa,threads}
{C,CXX,F77}FLAGS = -O2 -fomit-frame-pointer

Note that I killed the first loop-2c.c compilation that FAILed after some
98 CPU minutes (left the machine for lunch :) and the second one after some
3 CPU minutes. Isn't there a way to limit the running time of any
compilation/execution to something like 10 minutes to catch infinite loops?

WARNING: Couldn't find the global config file.
Test Run By broot on Tue Mar 24 02:28:46 1998
Native configuration is sparc-sun-solaris2.5.1

		=== libio tests ===

		=== libio Summary ===

# of expected passes		40

WARNING: Couldn't find the global config file.
Test Run By broot on Tue Mar 24 02:32:23 1998
Native configuration is sparc-sun-solaris2.5.1

		=== libstdc++ tests ===

FAIL: tmap.cc compilation
FAIL: tmap.cc -O compilation

		=== libstdc++ Summary ===

# of expected passes		24
# of unexpected failures	2
# of expected failures		4

WARNING: Couldn't find the global config file.
Test Run By broot on Tue Mar 24 02:35:58 1998
Native configuration is sparc-sun-solaris2.5.1

		=== gcc tests ===

FAIL: gcc.c-torture/execute/loop-2c.c compilation,  -O2 -fomit-frame-pointer -finline-functions -funroll-loops 
FAIL: gcc.c-torture/execute/loop-2c.c compilation,  -O2 -fomit-frame-pointer -finline-functions -funroll-all-loops 
FAIL: gcc.c-torture/execute/loop-2d.c compilation,  -O2 -fomit-frame-pointer -finline-functions -funroll-loops 
FAIL: gcc.c-torture/execute/loop-2d.c compilation,  -O2 -fomit-frame-pointer -finline-functions -funroll-all-loops 
FAIL: gcc.c-torture/execute/loop-2f.c execution,  -O2 
FAIL: gcc.c-torture/execute/loop-2f.c execution,  -O2 -fomit-frame-pointer -finline-functions 
FAIL: gcc.c-torture/execute/loop-2f.c execution,  -O2 -fomit-frame-pointer -finline-functions -funroll-loops 
FAIL: gcc.c-torture/execute/loop-2f.c execution,  -O2 -fomit-frame-pointer -finline-functions -funroll-all-loops 
FAIL: gcc.c-torture/execute/loop-2f.c execution,  -O2 -g 

		=== gcc Summary ===

# of expected passes		5994
# of unexpected failures	9
# of expected failures		6
# of untested testcases		4
# of unsupported tests		11

WARNING: Couldn't find the global config file.
Test Run By broot on Tue Mar 24 06:09:03 1998
Native configuration is sparc-sun-solaris2.5.1

		=== g++ tests ===

FAIL: g++.brendan/crash8.C (test for excess errors)
XPASS: g++.mike/ns3.C  (test for errors, line 1)
FAIL: g++.other/friend1.C (test for excess errors)
FAIL: g++.pt/explicit12.C (test for excess errors)
FAIL: g++.pt/explicit13.C (test for excess errors)
FAIL: g++.pt/memclass7.C (test for excess errors)
FAIL: g++.pt/spec10.C (test for excess errors)
FAIL: g++.pt/spec11.C (test for excess errors)
FAIL: g++.pt/spec12.C (test for excess errors)
FAIL: g++.pt/spec13.C (test for excess errors)
FAIL: g++.pt/spec15.C (test for excess errors)
FAIL: g++.pt/spec6.C no matching function (test for errors, line 25)
FAIL: g++.pt/spec6.C no matching function (test for errors, line 28)
FAIL: g++.pt/spec6.C (test for excess errors)
FAIL: g++.pt/vaarg.C  Execution test

		=== g++ Summary ===

# of expected passes		3725
# of unexpected failures	14
# of unexpected successes	1
# of expected failures		80
# of untested testcases		6

WARNING: Couldn't find the global config file.
Test Run By broot on Tue Mar 24 07:24:10 1998
Native configuration is sparc-sun-solaris2.5.1

		=== g77 tests ===

		=== g77 Summary ===

# of expected passes		168


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]