public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100067] Unexpected warning for -mcpu=neoverse-n1 when configured with --with-fpu
Date: Wed, 14 Apr 2021 10:00:32 +0000 [thread overview]
Message-ID: <bug-100067-4-ULyOnPVMwR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100067-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100067
--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Earnshaw <rearnsha@gcc.gnu.org>:
https://gcc.gnu.org/g:d1e4368ddb76a92c44f824c8e4ca1a3de8149342
commit r11-8168-gd1e4368ddb76a92c44f824c8e4ca1a3de8149342
Author: Richard Earnshaw <rearnsha@arm.com>
Date: Wed Apr 14 10:56:36 2021 +0100
arm: fix warning when -mcpu=neoverse-n1 is used with -mfpu=neon [PR100067]
If the compiler is configured with --with-fpu=<!auto> (or invoked
with, say, -mfpu=neon), then specifying -mcpu=neoverse-n1 can lead to
an unexpected warning: cc1: warning: switch â-mcpu=neoverse-n1â
conflicts with â-march=armv8.2-aâ switch
The fix for this is to correctly remove all the feature bits relating
to simd/fp units when -mfpu is used, not just those bits that form
part of the -mfpu specification (which is a subset).
gcc:
PR target/100067
* config/arm/arm.c (arm_configure_build_target): Strip
isa_all_fpbits
from the isa_delta when -mfpu has been used.
(arm_options_perform_arch_sanity_checks): It's the architecture
that
lacks an FPU not the processor.
next prev parent reply other threads:[~2021-04-14 10:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 17:40 [Bug target/100067] New: " rearnsha at gcc dot gnu.org
2021-04-14 10:00 ` cvs-commit at gcc dot gnu.org [this message]
2021-04-14 10:07 ` [Bug target/100067] " 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-ULyOnPVMwR@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: 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).