public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Toon Moene <toon@moene.indiv.nluug.nl>
To: egcs@cygnus.com
Subject: g77 in egcs: suboptimal results ?
Date: Tue, 19 Aug 1997 13:19:51 -0000	[thread overview]
Message-ID: <9708191319.AA21540@moene.indiv.nluug.nl> (raw)

>  Note that mdbnch (at least the version I know) is in
>  double precision.  Thus other performance considerations
>  are typically overshadowed on ppro by the double alignment
>  problems.  See the g77 manual.

Agree, but if he used the same g77 options as documented on the  
mdbnch Web page, this is not the cause:  -malign-double is listed  
there.

At first I thought that the absence of my performance patches would  
go a long way to explaining the results, but on my machine they  
make only a 1 % difference for this code.

[ Note that I can't say anything about egcs yet:  It doesn't build  
on my machine - I just compared the results of mdbnch.f when  
compiled with:

g77 -O2 -fforce-addr
(494 seconds)

and

g77 -O2 -fforce-addr -fno-rerun-loop-opt -fno-reduce-all-givs  
-fno-move-all-movables
(500 seconds)
]

using g77-0.5.21-970811 + gcc-2.7.2.2

HTH,
Toon.

                 reply	other threads:[~1997-08-19 13:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=9708191319.AA21540@moene.indiv.nluug.nl \
    --to=toon@moene.indiv.nluug.nl \
    --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).