From: Dave Love <d.love@dl.ac.uk>
To: egcs@cygnus.com
Subject: Re: EGCS-1.0.2 pre fails on Spec CPU 95
Date: Sun, 08 Mar 1998 12:12:00 -0000 [thread overview]
Message-ID: <rzqlnulkkm0.fsf@djlvig.dl.ac.uk> (raw)
In-Reply-To: <199803042254.OAA11600@proto.math.ucdavis.edu>
>>>>> "Bill" == Bill Broadley <bill@math.ucdavis.edu> writes:
Bill> Results are available on intel using the Intel reference
Bill> compiler which gets very good numbers.
Presumably it's tuned to be fast and correct for this case :-). I've
heard the Fortran compiler compared unfavourably to g77 elswhere...
Bill> egcs-1.0.1/g77 failed on -O2, but works with -O1.
Bill> egcs-1.0.2 worked with -O2 but did NOT work with -m486
Bill> -fomit-frame-pointer -O2 It finished all the benchmarks but one
Bill> then failed and produced the wrong output.
This sounds suspiciously like a numerical problem with the code. Is
it cured (with the expected slowdown) by -ffloat-store or other
options from the `Working Code' (?) node of the g77 manual? A
surprisingly large number of Fortran benchmarks have programming
problems of one sort or another which g77 exposes, although it's often
difficult to persuade people of this.
Bill> Unfortunately I can't give out the source,
What is the program at issue? Perhaps we can find source elsewhere
(if, as I understand, Spec is compiled from original freely-available
sources). Alternatively I can suggest sources of tools with which to
check it.
Regarding speed, the usual x86 problems with alignment of doubles
(when are we going to get that fixed??), -funroll-loops and
-fforce-addr at least may be relevant, but I don't know anything about
what's in spec95.
next prev parent reply other threads:[~1998-03-08 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-04 14:54 Bill Broadley
1998-03-08 12:12 ` Dave Love [this message]
1998-03-08 22:51 ` Jeffrey A Law
1998-03-09 4:44 ` Dave Love
1998-03-09 10:31 ` Jeffrey A Law
1998-03-10 11:36 ` Dave Love
[not found] <19980309091650.64067@dot.cygnus.com>
[not found] ` <199803091938.LAA29969@proto.math.ucdavis.edu>
1998-03-16 20:25 ` Richard Henderson
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=rzqlnulkkm0.fsf@djlvig.dl.ac.uk \
--to=d.love@dl.ac.uk \
--cc=egcs@cygnus.com \
/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).