From: Paul Furness <paul.furness@vil.ite.mee.com>
To: linux-admin@vger.kernel.org
Subject: Optimizing a compiler?
Date: 21 Oct 2002 16:20:35 +0100 [thread overview]
Message-ID: <1035213635.6421.74.camel@zebra.vil.ite.mee.com> (raw)
Sorry, this might be a little bit OT, but can anyone point me at some
useful info about how to compile code so that it uses the best speed
features of a given type of CPU?
I know that I can recompile the _kernel_ for and Athlon processor or an
intel P4 etc, but how do I optimize my own code which has nothing to do
with the kernel?
Do I need to change the code itself, or can I give gcc (in this case
g++) some options that tell it to use the best possible number crunching
code for my Athlon servers?
We're doing some research into video pattern recognition, so need to get
the absolute maximum possible number munching from our servers as a
single run take us at least 18 hours; every saved clock cycle adds up.
Thanks.
Paul.
--
Paul Furness
Systems Manager
2+2=5 for extremely large values of 2.
next reply other threads:[~2002-10-21 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 15:20 Paul Furness [this message]
2002-10-21 16:08 ` Optimizing a compiler? Glynn Clements
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=1035213635.6421.74.camel@zebra.vil.ite.mee.com \
--to=paul.furness@vil.ite.mee.com \
--cc=linux-admin@vger.kernel.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