public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Kito Cheng <kito@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-9143] doc: RISC-V: Document that -mcpu doesn't override -march or -mtune Date: Fri, 23 Feb 2024 04:27:07 +0000 (GMT) [thread overview] Message-ID: <20240223042707.932813858416@sourceware.org> (raw) https://gcc.gnu.org/g:1c5da882bf77400748aeb0b01bf9a7faba1a4f32 commit r14-9143-g1c5da882bf77400748aeb0b01bf9a7faba1a4f32 Author: Palmer Dabbelt <palmer@rivosinc.com> Date: Tue Feb 20 07:45:38 2024 -0800 doc: RISC-V: Document that -mcpu doesn't override -march or -mtune This came up recently as Edwin was looking through the test suite. A few of us were talking about this during the patchwork meeting and were surprised. Looks like this is the desired behavior, so let's at least document it. gcc/ChangeLog: * doc/invoke.texi: Document -mcpu. Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com> Diff: --- gcc/doc/invoke.texi | 2 ++ 1 file changed, 2 insertions(+) diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index 58527e1ea3c5..4f4ca2b76720 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -30750,6 +30750,8 @@ Permissible values for this option are: @samp{sifive-e20}, @samp{sifive-e21}, @samp{sifive-u54}, @samp{sifive-u74}, @samp{sifive-x280}, @samp{sifive-xp450}, @samp{sifive-x670}. +Note that @option{-mcpu} does not override @option{-march} or @option{-mtune}. + @opindex mtune @item -mtune=@var{processor-string} Optimize the output for the given processor, specified by microarchitecture or
reply other threads:[~2024-02-23 4:27 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240223042707.932813858416@sourceware.org \ --to=kito@gcc.gnu.org \ --cc=gcc-cvs@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).