public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/aoliva/heads/testme)] [PR104882] [arm] require mve hw for mve run test
Date: Thu, 23 Feb 2023 14:02:49 +0000 (GMT)	[thread overview]
Message-ID: <20230223140249.A98FB3857C45@sourceware.org> (raw)

https://gcc.gnu.org/g:257d025d19012766d4388ea76187ddbef7d53a1a

commit 257d025d19012766d4388ea76187ddbef7d53a1a
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Thu Feb 23 11:01:27 2023 -0300

    [PR104882] [arm] require mve hw for mve run test
    
    The pr104882.c test is an execution test, but arm_v8_1m_mve_ok only
    tests for compile-time support.  Add a requirement for mve hardware.
    
    
    for  gcc/testsuite/ChangeLog
    
            PR target/104882
            * gcc.target/arm/simd/pr104882.c: Require mve hardware.

Diff:
---
 gcc/testsuite/gcc.target/arm/simd/pr104882.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/gcc/testsuite/gcc.target/arm/simd/pr104882.c b/gcc/testsuite/gcc.target/arm/simd/pr104882.c
index ae9709af42f..1ea7a14836f 100644
--- a/gcc/testsuite/gcc.target/arm/simd/pr104882.c
+++ b/gcc/testsuite/gcc.target/arm/simd/pr104882.c
@@ -1,4 +1,5 @@
 /* { dg-do run } */
+/* { dg-require-effective-target arm_mve_hw } */
 /* { dg-require-effective-target arm_v8_1m_mve_ok } */
 /* { dg-add-options arm_v8_1m_mve } */
 /* { dg-additional-options "-O2" } */

             reply	other threads:[~2023-02-23 14:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23 14:02 Alexandre Oliva [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-03 18:47 Alexandre Oliva
2023-02-23 13:57 Alexandre Oliva
2023-02-23 13:49 Alexandre Oliva
2023-02-23 13:27 Alexandre Oliva
2023-02-16 11:13 Alexandre Oliva

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=20230223140249.A98FB3857C45@sourceware.org \
    --to=aoliva@gcc.gnu.org \
    --cc=gcc-cvs@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).