From: pancho@galaxy.lca.uevora.pt
To: Richard Henderson <rth@cygnus.com>, egcs@cygnus.com
Subject: Slow processing with g77 in egcs
Date: Mon, 05 Jan 1998 09:23:00 -0000 [thread overview]
Message-ID: <Pine.LNX.3.96.980105171553.30706C-100000@galaxy.lca.uevora.pt> (raw)
In-Reply-To: <19980102160709.14510@dot.cygnus.com>
Hi all,
I installed egcs-1.0 in a PC164-LX having a cpu 21164a (600 MHz) cache=4
MB ans RAM=512 MB.
I teste the machine with a f77 code that ran in several platforms.
For comparison this code was ran in a axp 255. and a PC164 LX with a cpu
500 MHz, running DU a DEC fortran. Results:
code in PC164LX with cpu 500 MHz was 7 times faster that in the axp255.
code in the PC164LX with cpu 600 MHz running linux and egcs is only 2.5
times faster than axp255.
So my question is: Whyt this difference? shouldn't the code be faster in
the 600 MHz?
I tryed all the flags tu make the code faster in the PC164LX with cpu 600
MHz.
I would appreciate any suggestions.
regards,
miguel
prev parent reply other threads:[~1998-01-05 9:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-02 12:19 error in alpha ev56 pancho
1998-01-02 16:09 ` Richard Henderson
1998-01-02 16:09 ` pancho
1998-01-02 16:44 ` pancho
1998-01-02 16:44 ` pancho
1998-01-05 9:23 ` pancho [this message]
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=Pine.LNX.3.96.980105171553.30706C-100000@galaxy.lca.uevora.pt \
--to=pancho@galaxy.lca.uevora.pt \
--cc=egcs@cygnus.com \
--cc=rth@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).