This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/18911] mmix-knuth-mmixware testsuite failure: g++.dg/init/array16.C execution
- From: "hp at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 23 Oct 2005 19:47:41 -0000
- Subject: [Bug target/18911] mmix-knuth-mmixware testsuite failure: g++.dg/init/array16.C execution
- References: <bug-18911-507@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #6 from hp at gcc dot gnu dot org 2005-10-23 19:47 -------
For the MMIX simulator on a 3.0 GHz P4, "time" shows:
mmix array16.exex 323.47s user 0.01s system 100% cpu 5:23.36 total
So, it *just* above the default time-out at 5min.
Comparing to a *slightly faster* simulator, the CGEN-generated one for
cris-elf, it's:
../../sim/cris/run array16.exex 14.44s user 0.01s system 99% cpu 14.459 total
So, it depends on the port and simulator whether the test can be reasonably
run.
(I've observed the array16 test to fail on my amd64 system exactly when
cpuspeed
is "stuck" at 1GHz rather than 2GHz due to some kernel bug.)
I'll adjust the test to compile-only for nonnative targets.
--
hp at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |hp at gcc dot gnu dot org
|dot org |
Status|NEW |ASSIGNED
Last reconfirmed|2005-10-23 19:27:08 |2005-10-23 19:47:41
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18911