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] Unexpected warning for -mcpu=neoverse-n1 when configured with --with-fpu Date: Thu, 15 Apr 2021 13:51:36 +0000 [thread overview] Message-ID: <bug-100067-4-MvT7kTb5qD@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 #4 from Richard Earnshaw <rearnsha at gcc dot gnu.org> --- (In reply to Christophe Lyon from comment #3) > Unfortunately this is causing many regressions in the GCC testsuite. Sigh! I'm not entirely surprised. I suspect most of this is testisms, though. > > For instance: > --target arm-none-linux-gnueabi > --with-mode arm > --with-cpu cortex-a9 > --with-fpu default > gcc.target/arm/armv8_2-fp16-neon-1.c is compiled with > -mfloat-abi=softfp -march=armv8.2-a+fp16 > > /gcc/testsuite/gcc.target/arm/armv8_2-fp16-neon-1.c: In function > 'test_vceqz_16x4': > /gcc/testsuite/gcc.target/arm/armv8_2-fp16-neon-1.c:139:13: warning: > implicit declaration of function 'vceqz_f16'; did you mean 'vceqq_u16'? > [-Wimplicit-function-declaration] > /gcc/testsuite/gcc.target/arm/armv8_2-fp16-neon-1.c:10:25: note: in > definition of macro 'MSTRCAT' > /gcc/testsuite/gcc.target/arm/armv8_2-fp16-neon-1.c:139:1: note: in > expansion of macro 'VCMP1_TEST' > /gcc/testsuite/gcc.target/arm/armv8_2-fp16-neon-1.c:139:13: error: > incompatible types when returning type 'int' but 'uint16x4_t' was expected > [...] It's not obvious what's happening here. I'll look. > > > --target arm-none-linux-gnueabi > --with-mode arm > --with-cpu cortex-a9 > --with-fpu default > Dejagnu flags: -march=armv5t > gcc.target/arm/aes-fuse-1.c is compiled with > > -march=armv5t -mfpu=crypto-neon-fp-armv8 -mfloat-abi=softfp -mcpu=cortex-a72 > cc1: warning: switch '-mcpu=cortex-a72' conflicts with switch '-march=armv5t' The warning is correct. That's a stupid combination to pass to the compiler (arch=armv5 and cpu=<armv8>). What's less clear is why this wasn't happening before.
next prev parent reply other threads:[~2021-04-15 13:51 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 ` [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 [this message] 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-MvT7kTb5qD@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).