public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/25305] [4.0 regression]: libfortran failed fma3d in SPEC CPU 2K
Date: Tue, 20 Dec 2005 17:01:00 -0000 [thread overview]
Message-ID: <20051220170107.12272.qmail@sourceware.org> (raw)
In-Reply-To: <bug-25305-682@http.gcc.gnu.org/bugzilla/>
------- Comment #22 from kargl at gcc dot gnu dot org 2005-12-20 17:01 -------
The testcase isn't needed and should not be committed.
As explained elsewhere, the problem was caused by merging
one line from a 4.1 patch into 4.0 that should not have
been committed. Jerry has fixed that problem. With very
limited gfortran manpower, gfortran 4.0.x will see very few
if any new changes.
In fact, using gfortran 4.0.x to obtain SPEC benchmarks is
actually rather stupid. Do yourself a favor and upgrade to
gfortran 4.1 (pre-release).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25305
next prev parent reply other threads:[~2005-12-20 17:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 1:45 [Bug target/25305] New: [4.0]: -O2 miscompiled " hjl at lucon dot org
2005-12-08 1:56 ` [Bug target/25305] [4.0 regression]: " hjl at lucon dot org
2005-12-08 2:04 ` hjl at lucon dot org
2005-12-08 2:11 ` hjl at lucon dot org
2005-12-08 3:16 ` hjl at lucon dot org
2005-12-08 3:28 ` hjl at lucon dot org
2005-12-08 3:30 ` hjl at lucon dot org
2005-12-08 6:55 ` [Bug libfortran/25305] [4.0 regression]: libfortran failed " hjl at lucon dot org
2005-12-08 9:01 ` Jerry DeLisle
2005-12-08 7:32 ` hjl at lucon dot org
2005-12-08 9:01 ` jvdelisle at verizon dot net
2005-12-12 15:04 ` hjl at lucon dot org
2005-12-19 7:25 ` jvdelisle at gcc dot gnu dot org
2005-12-19 14:40 ` hjl at lucon dot org
2005-12-19 14:41 ` grigory_zagorodnev at linux dot intel dot com
2005-12-20 0:50 ` jvdelisle at gcc dot gnu dot org
2005-12-20 5:06 ` jvdelisle at gcc dot gnu dot org
2005-12-20 6:06 ` jvdelisle at gcc dot gnu dot org
2005-12-20 6:12 ` jvdelisle at gcc dot gnu dot org
2005-12-20 6:19 ` jvdelisle at gcc dot gnu dot org
2005-12-20 6:22 ` hjl at lucon dot org
2005-12-20 6:48 ` steven at gcc dot gnu dot org
2005-12-20 14:44 ` hjl at lucon dot org
2005-12-20 17:01 ` kargl at gcc dot gnu dot org [this message]
2006-01-01 5:28 ` pinskia at gcc dot gnu dot 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=20051220170107.12272.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).