public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mkuvyrkov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/114307] [ARM] Vectorization tests not disabled for vector-less targets Date: Tue, 12 Mar 2024 16:12:39 +0000 [thread overview] Message-ID: <bug-114307-4-58RtTR5QsD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114307-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114307 --- Comment #5 from Maxim Kuvyrkov <mkuvyrkov at gcc dot gnu.org> --- Thanks to Christophe L. for explaining the logic behind "is-effective-target arm_neon_ok". The issue is that "/* { dg-options "-O3" } */" in pr113576.c overrides DEFAULT_VECTFLAGS set by check_vect_support_and_set_flags, which contains "-mfpu=neon" -- as added by "is-effective-target arm_neon_ok". It so happens that pr113576.c is the only test that both uses "dg-options" and "tree-vect.h", thus the new error.
next prev parent reply other threads:[~2024-03-12 16:12 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-11 16:13 [Bug target/114307] New: [ARM] GCC generates instruction that assembler rejects mkuvyrkov at gcc dot gnu.org 2024-03-11 17:34 ` [Bug target/114307] " rearnsha at gcc dot gnu.org 2024-03-11 17:35 ` rearnsha at gcc dot gnu.org 2024-03-11 21:36 ` [Bug testsuite/114307] " pinskia at gcc dot gnu.org 2024-03-12 14:45 ` mkuvyrkov at gcc dot gnu.org 2024-03-12 16:12 ` mkuvyrkov at gcc dot gnu.org [this message] 2024-03-12 17:13 ` [Bug testsuite/114307] [ARM] Vectorization tests not disabled for vector-less targets pinskia at gcc dot gnu.org 2024-03-13 6:24 ` mkuvyrkov at gcc dot gnu.org 2024-03-13 11:03 ` mkuvyrkov at gcc dot gnu.org 2024-03-28 13:44 ` cvs-commit at gcc dot gnu.org 2024-03-28 13:50 ` mkuvyrkov 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-114307-4-58RtTR5QsD@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).