public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/5900] [g77 & gfortran] Lapack regressions since g77 2.95.2
Date: Mon, 17 Oct 2005 02:02:00 -0000 [thread overview]
Message-ID: <20051017020220.6207.qmail@sourceware.org> (raw)
In-Reply-To: <bug-5900-849@http.gcc.gnu.org/bugzilla/>
------- Comment #52 from jvdelisle at gcc dot gnu dot org 2005-10-17 02:02 -------
I would like to propose that this bug be closed. This is about as good as it
gets. We should set up some automatic regression testing on LAPACK from hence
forth.
With -O1 -march=pentium4:
csep.out: CST drivers: 1 out of 11664 tests failed to pass the threshold
dgd.out: DXV drivers: 200 out of 5000 tests failed to pass the threshold
sgd.out: SXV drivers: 37 out of 5000 tests failed to pass the threshold
ssep.out: SST: 1 out of 4662 tests failed to pass the threshold
ssep.out: SST drivers: 1 out of 14256 tests failed to pass the threshold
zgd.out: ZXV drivers: 24 out of 5000 tests failed to pass the threshold
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=5900
next prev parent reply other threads:[~2005-10-17 2:02 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-5900-849@http.gcc.gnu.org/bugzilla/>
2005-10-03 12:50 ` fxcoudert at gcc dot gnu dot org
2005-10-17 2:02 ` jvdelisle at gcc dot gnu dot org [this message]
2005-10-17 2:45 ` david dot billinghurst at comalco dot riotinto dot com dot au
2005-10-23 21:19 ` steven at gcc dot gnu dot org
2006-01-01 2:50 ` jvdelisle at gcc dot gnu dot org
2006-06-01 7:31 ` paul dot richard dot thomas at cea dot fr
2006-06-02 0:17 ` jvdelisle at gcc dot gnu dot org
[not found] <20020309112600.5900.schmid@snake.iap.physik.tu-darmstadt.de>
2004-09-23 19:37 ` toon at moene dot indiv dot nluug dot nl
2004-09-27 19:56 ` tobi at gcc dot gnu dot org
2004-12-14 16:08 ` Thomas dot Koenig at online dot de
2004-12-14 16:14 ` Thomas dot Koenig at online dot de
2005-01-04 6:29 ` jvdelisle at verizon dot net
2005-01-04 7:15 ` jvdelisle at verizon dot net
2005-01-04 9:30 ` Thomas dot Koenig at online dot de
2005-01-06 14:39 ` tobi at gcc dot gnu dot org
2005-01-08 14:41 ` Thomas dot Koenig at online dot de
2005-01-10 4:46 ` jvdelisle at verizon dot net
2005-01-12 4:22 ` giovannibajo at libero dot it
2005-01-20 10:58 ` Thomas dot Koenig at online dot de
2005-01-20 11:01 ` Thomas dot Koenig at online dot de
2005-01-20 22:22 ` billingd at gcc dot gnu dot org
2005-01-20 22:38 ` billingd at gcc dot gnu dot org
2005-01-21 1:18 ` jvdelisle at verizon dot net
2005-01-24 9:13 ` jakub at gcc dot gnu dot org
2005-01-24 22:48 ` billingd at gcc dot gnu dot org
2005-01-25 0:15 ` billingd at gcc dot gnu dot org
2005-01-25 2:07 ` billingd at gcc dot gnu dot org
2005-01-25 6:00 ` jvdelisle at verizon dot net
2005-01-26 9:22 ` Thomas dot Koenig at online dot de
2005-01-26 9:42 ` Thomas dot Koenig at online dot de
2005-01-31 14:39 ` Thomas dot Koenig at online dot de
2005-02-01 7:52 ` jvdelisle at verizon dot net
2005-02-01 8:10 ` jvdelisle at verizon dot net
2005-02-02 3:29 ` jvdelisle at verizon dot net
2005-02-07 22:06 ` Thomas dot Koenig at online dot de
2005-02-08 0:15 ` giovannibajo at libero dot it
2005-02-08 14:12 ` jvdelisle at verizon dot net
2005-02-08 15:12 ` jvdelisle at verizon dot net
2005-02-08 16:04 ` Thomas dot Koenig at online dot de
2005-02-08 17:16 ` giovannibajo at libero dot it
2005-02-08 21:35 ` Thomas dot Koenig at online dot de
2005-02-08 23:57 ` Thomas dot Koenig at online dot de
2005-02-09 13:58 ` Thomas dot Koenig at online dot de
2005-02-09 18:08 ` Thomas dot Koenig at online dot de
2005-02-10 16:14 ` Thomas dot Koenig at online dot de
2005-02-10 23:11 ` Thomas dot Koenig at online dot de
2005-02-11 13:39 ` jvdelisle at verizon dot net
2005-02-11 15:20 ` jvdelisle at verizon dot net
2005-02-11 15:25 ` jvdelisle at verizon dot net
2005-02-11 17:22 ` Thomas dot Koenig at online dot de
2005-02-11 17:23 ` Thomas dot Koenig at online dot de
2005-02-19 12:58 ` wilson at gcc dot gnu dot org
2005-02-24 14:31 ` rth at gcc dot gnu dot org
2005-02-28 14:55 ` billingd at gcc dot gnu dot org
2005-03-02 0:07 ` billingd at gcc dot gnu dot org
2005-03-02 0:09 ` billingd at gcc dot gnu dot org
2005-03-02 3:56 ` billingd at gcc dot gnu dot org
2005-03-31 21:38 ` rth at gcc dot gnu dot org
2005-04-29 14:03 ` fxcoudert at gcc dot gnu dot org
2005-04-30 5:06 ` jvdelisle at verizon dot net
2005-05-02 10:06 ` fxcoudert at gcc dot gnu dot org
2005-06-08 6:04 ` jvdelisle at verizon dot net
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=20051017020220.6207.qmail@sourceware.org \
--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).