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 testsuite/104730] gcc.dg/vect/complex/pr102819-9.c FAILs Date: Wed, 02 Mar 2022 12:55:05 +0000 [thread overview] Message-ID: <bug-104730-4-vB8kXkLKvh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104730-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104730 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Tamar Christina <tnfchris@gcc.gnu.org>: https://gcc.gnu.org/g:8eb36ce5576817c54ad1f8061d2232774fc0d093 commit r11-9635-g8eb36ce5576817c54ad1f8061d2232774fc0d093 Author: Tamar Christina <tamar.christina@arm.com> Date: Wed Mar 2 12:49:57 2022 +0000 vect: add vect_float to pr102819 tests This adds a vect_float requirements to this tests to stop them from running on targets that don't support float vectorization. gcc/testsuite/ChangeLog: PR testsuite/104730 * gcc.dg/vect/complex/pr102819-1.c: Add vect_float. * gcc.dg/vect/complex/pr102819-2.c: Likewise. * gcc.dg/vect/complex/pr102819-3.c: Likewise. * gcc.dg/vect/complex/pr102819-4.c: Likewise. * gcc.dg/vect/complex/pr102819-5.c: Likewise. * gcc.dg/vect/complex/pr102819-6.c: Likewise. * gcc.dg/vect/complex/pr102819-7.c: Likewise. * gcc.dg/vect/complex/pr102819-8.c: Likewise. * gcc.dg/vect/complex/pr102819-9.c: Likewise.
next prev parent reply other threads:[~2022-03-02 12:55 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-01 10:34 [Bug tree-optimization/104730] New: " ro at gcc dot gnu.org 2022-03-01 10:36 ` [Bug tree-optimization/104730] " ro at gcc dot gnu.org 2022-03-01 10:36 ` ro at gcc dot gnu.org 2022-03-01 10:40 ` [Bug testsuite/104730] " tnfchris at gcc dot gnu.org 2022-03-01 13:58 ` rguenth at gcc dot gnu.org 2022-03-02 12:51 ` cvs-commit at gcc dot gnu.org 2022-03-02 12:55 ` cvs-commit at gcc dot gnu.org [this message] 2022-03-02 12:57 ` tnfchris 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-104730-4-vB8kXkLKvh@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).