public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/45988] New: gfortran.dg/vect/fast-math-pr38968.f90 times out on 32-bit Solaris 10/x86
Date: Tue, 12 Oct 2010 18:04:00 -0000 [thread overview]
Message-ID: <bug-45988-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45988
Summary: gfortran.dg/vect/fast-math-pr38968.f90 times out on
32-bit Solaris 10/x86
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: ro@gcc.gnu.org
Host: i386-pc-solaris2.10
Target: i386-pc-solaris2.10
Build: i386-pc-solaris2.10
The 32-bit gfortran.dg/vect/fast-math-pr38968.f90 execution test regularly
times
out on Solaris 10/x86:
WARNING: program timed out.
FAIL: gfortran.dg/vect/fast-math-pr38968.f90 execution test
at least when run with a make -j16 -k check on a Sun Fire X4450 (4 x Xeon
X7350,
2.93 GHz).
When run on an otherwise idle machine, it takes about 1:31 min, well below the
default dejagnu timeout of 5 minutes. Perhaps the timeout factor 4.0 that was
present until 4.5 needs to be reinstantiated?
next reply other threads:[~2010-10-12 18:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 18:04 ro at gcc dot gnu.org [this message]
2010-12-27 0:52 ` [Bug testsuite/45988] " dfranke at gcc dot gnu.org
2011-01-24 9:46 ` ro at gcc dot gnu.org
2011-01-24 9:55 ` ro at gcc dot gnu.org
2012-03-02 16:24 ` ro at gcc dot gnu.org
2012-03-02 16:27 ` ro at gcc dot gnu.org
2012-03-02 16:27 ` ro at gcc dot gnu.org
2012-03-02 16:29 ` [Bug target/45988] " ro at gcc dot gnu.org
2012-03-04 0:58 ` pinskia at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-45988-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).