public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Christophe Lyon <clyon@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-2170] testsuite: Add arm_arch_v7a_ok effective-target to pr57351.c
Date: Thu,  8 Jul 2021 13:54:49 +0000 (GMT)	[thread overview]
Message-ID: <20210708135449.8A992398D060@sourceware.org> (raw)

https://gcc.gnu.org/g:1ca642d785c49e9e0b28651b190720267703f023

commit r12-2170-g1ca642d785c49e9e0b28651b190720267703f023
Author: Christophe Lyon <christophe.lyon@foss.st.com>
Date:   Wed Jun 30 13:47:07 2021 +0000

    testsuite: Add arm_arch_v7a_ok effective-target to pr57351.c
    
    I've noticed that overriding cpu/arch flags when running the testsuite
    can cause this test to fail rather than being skipped because of
    incompatible flags combination.
    
    Since the test forces -march=armv7-a, make sure it is accepted in
    combination with the current runtestflags.
    
    2021-07-08  Christophe Lyon  <christophe.lyon@foss.st.om>
    
            gcc/testsuite/
            * gcc.dg/debug/pr57351.c: Require arm_arch_v7a_ok
            effective-target.

Diff:
---
 gcc/testsuite/gcc.dg/debug/pr57351.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/gcc/testsuite/gcc.dg/debug/pr57351.c b/gcc/testsuite/gcc.dg/debug/pr57351.c
index 972f3e9ebec..236d74ddedb 100644
--- a/gcc/testsuite/gcc.dg/debug/pr57351.c
+++ b/gcc/testsuite/gcc.dg/debug/pr57351.c
@@ -1,5 +1,6 @@
 /* { dg-do compile } */
 /* { dg-require-effective-target arm_neon }  */
+/* { dg-require-effective-target arm_arch_v7a_ok }  */
 /* { dg-options "-std=c99 -Os -g -march=armv7-a" } */
 /* { dg-add-options arm_neon } */


                 reply	other threads:[~2021-07-08 13:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210708135449.8A992398D060@sourceware.org \
    --to=clyon@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).