With LAST_UPDATED: "Thu Dec 9 10:50:49 UTC 2004" I get:
WARNING: program timed out.
FAIL: g++.dg/init/array16.C execution test
No particular hint in g++.log.
The host machine is a Celeron 2.6GHz.
This is a new test, introduced between "Thu Dec 9 03:56:14 UTC 2004"
and above. Looking at the test, it seems it is simply a bit too long
execution-wise and at least not fit for simulator targets.
Does it really need e.g. in the order of 4e6 iterations to accomplish
its goal? Or can that number be divided by say 10000;
s/elt buffer[4111222]/elt buffer[411]/ ?
--
Summary: mmix-knuth-mmixware testsuite failure:
g++.dg/init/array16.C execution
Product: gcc
Version: 4.0.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: target
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: hp at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org,nathan at gcc dot gnu
dot org
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: mmix-knuth-mmixware
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18911
