From: Michael Roth <mroth@nessie.de>
To: gcc-help@gcc.gnu.org
Subject: How to tune gcc for different x86 host and target cpus?
Date: Fri, 23 Apr 2004 11:50:00 -0000 [thread overview]
Message-ID: <40890299.1070608@nessie.de> (raw)
Hello,
as far as I understand, when building gcc, I can use --with-arch=pentium
to tell configure that the resulting compiler should emit code optimized
for pentium processors.
But how can I tell the configure script that the compiler itself should
be optimized for a different cpu architecture?
Example #1: Host and build are athlon-xp, target should be pentium.
Example #2: Build is pentium4, Host should be pentium-mmx, target should
be 386.
What configure options should I use? (Host, build and target are all
linux systems, but I think this apply to every system with x86 processor
variants?)
Michael Roth
next reply other threads:[~2004-04-23 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 11:50 Michael Roth [this message]
2004-04-25 0:56 ` Ian Lance Taylor
2004-05-12 19:45 ` Michael Roth
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=40890299.1070608@nessie.de \
--to=mroth@nessie.de \
--cc=gcc-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).