public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bogden at arm dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/59718] New: Behaviour of -mcpu documented incorrectly for ARM targets Date: Wed, 08 Jan 2014 11:34:00 -0000 [thread overview] Message-ID: <bug-59718-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59718 Bug ID: 59718 Summary: Behaviour of -mcpu documented incorrectly for ARM targets Product: gcc Version: 4.8.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: bogden at arm dot com I am given to understand that the behaviour of the -mcpu option for both the ARM and AArch64 targets is that it is a shorthand for specifying -march=foo -mtune=bar, where bar is a CPU that implements foo. However, the documentation for AArch64 (gcc-4.8.2/gcc/AArch64-Options.html#AArch64-Options) says that -mcpu is the same as -march, except that it takes CPU names rather than architecture versions. http://gcc.gnu.org/onlinedocs/gcc-4.8.2/gcc/ARM-Options.html#ARM-Options is similar except that it seems to describe the correct behaviour in one specific case. These sections should be rewritten to correctly describe the behaviour of -mcpu.
next reply other threads:[~2014-01-08 11:34 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-08 11:34 bogden at arm dot com [this message] 2014-01-08 11:59 ` [Bug target/59718] " rearnsha at gcc dot gnu.org 2014-02-05 11:43 ` jgreenhalgh at gcc dot gnu.org 2014-02-05 14:41 ` jgreenhalgh at gcc dot gnu.org 2014-02-05 14:55 ` jgreenhalgh at gcc dot gnu.org 2014-02-05 15:03 ` jgreenhalgh at gcc dot gnu.org
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=bug-59718-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).