From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11497 invoked by alias); 23 Oct 2005 19:47:44 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 11481 invoked by uid 48); 23 Oct 2005 19:47:41 -0000 Date: Sun, 23 Oct 2005 19:47:00 -0000 Message-ID: <20051023194741.11480.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug target/18911] mmix-knuth-mmixware testsuite failure: g++.dg/init/array16.C execution In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "hp at gcc dot gnu dot org" X-SW-Source: 2005-10/txt/msg03017.txt.bz2 List-Id: ------- 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