public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/100067] New: Unexpected warning for -mcpu=neoverse-n1 when configured with --with-fpu Date: Tue, 13 Apr 2021 17:40:43 +0000 [thread overview] Message-ID: <bug-100067-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100067 Bug ID: 100067 Summary: Unexpected warning for -mcpu=neoverse-n1 when configured with --with-fpu Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: rearnsha at gcc dot gnu.org Target Milestone: --- If the compiler is configured with (for example): --with-arch=armv7-a --with-fpu=neon --with-float=hard then compiling with gcc -S -mcpu=neoverse-n1 <any-c-file> leads to an unexpected warning: cc1: warning: switch ‘-mcpu=neoverse-n1’ conflicts with ‘-march=armv8.2-a’ switch The same can be seen if -mfpu is passed explicitly on the command-line (which, while it shouldn't happen, is slightly less surprising). If -mfpu is specified to be anything other than auto (via command line or configuration), it is expected that this will override *all* features from the cpu/arch setting that relate to the use of the FPU. Note, we should probably at this point progress the deprecation process for -mfpu by deprecating the config option that allows this to be set during configure.
next reply other threads:[~2021-04-13 17:40 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-13 17:40 rearnsha at gcc dot gnu.org [this message] 2021-04-14 10:00 ` [Bug target/100067] " cvs-commit at gcc dot gnu.org 2021-04-14 10:07 ` rearnsha at gcc dot gnu.org 2021-04-15 13:29 ` clyon at gcc dot gnu.org 2021-04-15 13:51 ` rearnsha at gcc dot gnu.org 2021-04-15 14:12 ` clyon at gcc dot gnu.org 2021-04-16 11:00 ` cvs-commit at gcc dot gnu.org 2021-04-19 17:00 ` cvs-commit 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-100067-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).