From: n8tm@aol.comnojunk (Tim Prince)
To: help-gcc@gnu.org
Subject: Re: optimisation and AMD K7
Date: Mon, 27 Dec 1999 08:37:00 -0000 [thread overview]
Message-ID: <19991227113203.01035.00001790@ng-ch1.aol.com> (raw)
In-Reply-To: <Pine.LNX.3.96.991227133931.17421A-100000@prope.insa-lyon.fr>
>Which version of gcc or egcs and which
>options should I use to get the best perf or the smaller exe.
Your mileage surely will vary. gcc-2.95.2 does well on many examples; gcc-2.96
improves significantly in certain situations, and loses in others.
On x86 architectures, the option -Os, which is intended to produce smallest
code, often produces faster code as well, possibly in combination with
-funroll-loops or -funroll-all-loops.
I believe 2.96 has seen some work for k7. With 2.96, the combination
-march=pentiumpro -ffast-math activates conditional moves and the like, as well
as a number of bugs. The latest version of 2.96 has corrected some of the code
alignment problems of 2.95.2.
Tim Prince
tprince@computer.org
WARNING: multiple messages have this Message-ID
From: n8tm@aol.comnojunk (Tim Prince)
To: help-gcc@gnu.org
Subject: Re: optimisation and AMD K7
Date: Fri, 31 Dec 1999 22:24:00 -0000 [thread overview]
Message-ID: <19991227113203.01035.00001790@ng-ch1.aol.com> (raw)
Message-ID: <19991231222400.lOIWgLQR5-puRUIYN8YVLA7QmUvFPA5ZFnD8ULJmy4A@z> (raw)
In-Reply-To: <Pine.LNX.3.96.991227133931.17421A-100000@prope.insa-lyon.fr>
>Which version of gcc or egcs and which
>options should I use to get the best perf or the smaller exe.
Your mileage surely will vary. gcc-2.95.2 does well on many examples; gcc-2.96
improves significantly in certain situations, and loses in others.
On x86 architectures, the option -Os, which is intended to produce smallest
code, often produces faster code as well, possibly in combination with
-funroll-loops or -funroll-all-loops.
I believe 2.96 has seen some work for k7. With 2.96, the combination
-march=pentiumpro -ffast-math activates conditional moves and the like, as well
as a number of bugs. The latest version of 2.96 has corrected some of the code
alignment problems of 2.95.2.
Tim Prince
tprince@computer.org
next prev parent reply other threads:[~1999-12-27 8:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-27 4:51 Jean Francois PARIS
1999-12-27 8:37 ` Tim Prince [this message]
1999-12-31 22:24 ` Tim Prince
2000-01-02 20:20 ` David Edelsohn
2000-04-01 0:00 ` David Edelsohn
1999-12-31 22:24 ` Jean Francois PARIS
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=19991227113203.01035.00001790@ng-ch1.aol.com \
--to=n8tm@aol.comnojunk \
--cc=help-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).