From: NightStrike <nightstrike@gmail.com>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: Clarification on mcpu/tune/arch options
Date: Fri, 14 Dec 2007 00:09:00 -0000 [thread overview]
Message-ID: <b609cb3b0712131609s3d98a79fpa1f13682557ebffd@mail.gmail.com> (raw)
The gcc manual defines the options mcpu, mtune, and march as being
optimizers for various ARM targets. It lists viable options, and they
are all ARM related. However, I often see people using options that
aren't in the manual for targets that the manual says aren't
supported. For instance, -mcpu=i686, or -march=native. What is the
nature of this discrepancy between the documentation and what I see as
common usage?
next reply other threads:[~2007-12-14 0:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 0:09 NightStrike [this message]
2007-12-14 0:24 ` John (Eljay) Love-Jensen
2007-12-14 0:45 ` NightStrike
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=b609cb3b0712131609s3d98a79fpa1f13682557ebffd@mail.gmail.com \
--to=nightstrike@gmail.com \
--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).