public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Richard Biener <rguenth@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r11-10037] testsuite: Skip pr105250.c for powerpc and s390 [PR105266]
Date: Fri, 27 May 2022 05:59:25 +0000 (GMT)	[thread overview]
Message-ID: <20220527055925.21648385608B@sourceware.org> (raw)

https://gcc.gnu.org/g:186fcf8b7a7c17a8a17466bc9149b3ca4ca9dd3e

commit r11-10037-g186fcf8b7a7c17a8a17466bc9149b3ca4ca9dd3e
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Sun Apr 17 21:34:51 2022 -0500

    testsuite: Skip pr105250.c for powerpc and s390 [PR105266]
    
    This test case pr105250.c is like its related pr105140.c, which
    suffers the error with message like "{AltiVec,vector} argument
    passed to unprototyped" on powerpc and s390.  So like commits
    r12-8025 and r12-8039, this fix is to add the dg-skip-if for
    powerpc*-*-* and s390*-*-*.
    
    gcc/testsuite/ChangeLog:
    
            PR testsuite/105266
            * gcc.dg/pr105250.c: Skip for powerpc*-*-* and s390*-*-*.
    
    (cherry picked from commit 021b51814d67bedd8f41ac07edfd05654140c6e5)

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

diff --git a/gcc/testsuite/gcc.dg/pr105250.c b/gcc/testsuite/gcc.dg/pr105250.c
index 665dd95d8cb..4683e0e63a2 100644
--- a/gcc/testsuite/gcc.dg/pr105250.c
+++ b/gcc/testsuite/gcc.dg/pr105250.c
@@ -1,5 +1,6 @@
 /* { dg-do compile } */
 /* { dg-options "-w -Wno-psabi -O2" } */
+/* { dg-skip-if "PR105266" { powerpc*-*-* s390*-*-* } } */
 
 typedef int __attribute__((__vector_size__(4))) T;
 typedef int __attribute__((__vector_size__(8))) U;


                 reply	other threads:[~2022-05-27  5:59 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=20220527055925.21648385608B@sourceware.org \
    --to=rguenth@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).