public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Robin Dapp <rdapp@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r11-8219] testsuite: Move gimplefe-4[0|1] tests.
Date: Fri, 16 Apr 2021 14:34:08 +0000 (GMT)	[thread overview]
Message-ID: <20210416143408.604DA3858034@sourceware.org> (raw)

https://gcc.gnu.org/g:eb8c931e0dbf1d7d9bc1279cab68a963e8f3c299

commit r11-8219-geb8c931e0dbf1d7d9bc1279cab68a963e8f3c299
Author: Robin Dapp <rdapp@linux.ibm.com>
Date:   Wed Mar 17 09:08:42 2021 +0100

    testsuite: Move gimplefe-4[0|1] tests.
    
    The gimplefe-40.c and gimplefe-41.c test cases require vect_* effective
    targets even though they reside in gcc.dg.  By default e.g.
    DEFAULT_VECTCFLAGS which is used to add target-specific machine or build
    flags is only applied in the ./vect subdirectory.  Move these tests
    there.
    
    gcc/testsuite/ChangeLog:
    
            * gcc.dg/gimplefe-40.c: Moved to...
            * gcc.dg/vect/gimplefe-40.c: ...here.
            * gcc.dg/gimplefe-41.c: Moved to...
            * gcc.dg/vect/gimplefe-41.c: ...here.

Diff:
---
 gcc/testsuite/gcc.dg/{ => vect}/gimplefe-40.c | 0
 gcc/testsuite/gcc.dg/{ => vect}/gimplefe-41.c | 0
 2 files changed, 0 insertions(+), 0 deletions(-)

diff --git a/gcc/testsuite/gcc.dg/gimplefe-40.c b/gcc/testsuite/gcc.dg/vect/gimplefe-40.c
similarity index 100%
rename from gcc/testsuite/gcc.dg/gimplefe-40.c
rename to gcc/testsuite/gcc.dg/vect/gimplefe-40.c
diff --git a/gcc/testsuite/gcc.dg/gimplefe-41.c b/gcc/testsuite/gcc.dg/vect/gimplefe-41.c
similarity index 100%
rename from gcc/testsuite/gcc.dg/gimplefe-41.c
rename to gcc/testsuite/gcc.dg/vect/gimplefe-41.c


                 reply	other threads:[~2021-04-16 14:34 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=20210416143408.604DA3858034@sourceware.org \
    --to=rdapp@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).