From: Toon Moene <toon@moene.indiv.nluug.nl>
To: Alexey Starovoytov <stork@sun.com>
Cc: Andi Kleen <ak@suse.de>, gcc@gcc.gnu.org
Subject: Re: contribution
Date: Fri, 12 Apr 2002 15:15:00 -0000 [thread overview]
Message-ID: <3CB74859.7FEB50D0@moene.indiv.nluug.nl> (raw)
In-Reply-To: <Pine.GSO.4.31.0204121042030.15886-100000@boojum>
Alexey Starovoytov wrote:
> On 12 Apr 2002, Andi Kleen wrote:
> > You could compiled 172.mgrid with gcc twice this way and it showed 48%
> > improvement ? Or did you use a different compiler as backend?
> It was gcc3.0.4 as a backend.
mgrid is one of those codes that heavily pays for reruning loop
optimisation (as it is now).
At least looking at the generated assembler, g77 -O2 -fno-rerun-loop-opt
produces much better code.
--
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
Join GNU Fortran 95: http://g95.sourceforge.net/ (under construction)
next prev parent reply other threads:[~2002-04-12 20:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.31.0204112030350.15026-101000@boojum.suse.lists.egcs-patches>
2002-04-12 1:28 ` contribution Andi Kleen
2002-04-12 11:42 ` contribution Alexey Starovoytov
2002-04-12 15:15 ` Toon Moene [this message]
2002-04-12 5:45 contribution Toon Moene
[not found] <3CB6D448.45A4FE3E@knmi.nl.suse.lists.egcs>
2002-04-12 5:54 ` contribution Andi Kleen
2002-04-12 5:58 ` contribution Toon Moene
[not found] <CAOw3FZBzjtxEmbSMJDviD-td4bDM_mCMs9BQpk0SvK4EpR8N5g@mail.gmail.com>
2022-03-14 8:35 ` Fwd: Contribution farhad
2022-03-14 16:51 ` Contribution David Edelsohn
2022-12-14 15:32 Contribution Mohamed Atef
2022-12-15 14:47 ` Contribution Jason Merrill
2022-12-15 16:42 ` Contribution Paul Smith
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=3CB74859.7FEB50D0@moene.indiv.nluug.nl \
--to=toon@moene.indiv.nluug.nl \
--cc=ak@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=stork@sun.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).