From: Andreas Jaeger <aj@suse.de>
To: gcc@gcc.gnu.org
Subject: -fno-rerun-loop-opt on current CVS version
Date: Mon, 10 Sep 2001 11:42:00 -0000 [thread overview]
Message-ID: <u81yleevll.fsf@gromit.moeb> (raw)
Toon asked me to check the effects of -fno-rerun-loop-opt. Here're
the results of SPECfp2000 on an 1.133 Ghz Athlon running SuSE Linux
7.2.
Base flags: -O2 -march=athlon -malign-double
Peak flags: -O2 -march=athlon -malign-double
(cont.) -fno-rerun-loop-opt
Estimated Estimated
Base Base Base Peak Peak Peak
Benchmarks Ref Time Run Time Ratio Ref Time Run Time Ratio
------------ -------- -------- -------- -------- -------- --------
168.wupwise 1600 419 382* 1600 403 397*
171.swim 3100 1005 308* 3100 1065 291*
172.mgrid 1800 1017 177* 1800 1038 173*
173.applu 2100 761 276* 2100 782 269*
177.mesa 1400 307 456* 1400 309 453*
179.art 2600 1856 140* 2600 1787 145*
183.equake 1300 449 289* 1300 449 290*
188.ammp 2200 784 281* 2200 804 274*
200.sixtrack 1100 563 195* 1100 521 211*
301.apsi 2600 1089 239* 2600 1098 237*
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
reply other threads:[~2001-09-10 11:42 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=u81yleevll.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=gcc@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).