public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Rainer Orth <ro@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-5321] testsuite: Fix gcc.dg/vect/vect-bitfield-write-[23].c on SPARC [PR107808]
Date: Tue, 24 Jan 2023 07:50:10 +0000 (GMT)	[thread overview]
Message-ID: <20230124075010.6F4D63858D33@sourceware.org> (raw)

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

commit r13-5321-ge304e9283a97e28dc0074d8d30715d3f626b4e87
Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Date:   Tue Jan 24 08:49:44 2023 +0100

    testsuite: Fix gcc.dg/vect/vect-bitfield-write-[23].c on SPARC [PR107808]
    
    The gcc.dg/vect/vect-bitfield-write-[23].c tests FAIL on 32 and 64-bit
    SPARC:
    
    FAIL: gcc.dg/vect/vect-bitfield-write-2.c -flto -ffat-lto-objects
    scan-tree-dump-times vect "vectorized 1 loops" 1
    FAIL: gcc.dg/vect/vect-bitfield-write-2.c scan-tree-dump-times vect
    "vectorized 1 loops" 1
    FAIL: gcc.dg/vect/vect-bitfield-write-3.c -flto -ffat-lto-objects
    scan-tree-dump-times vect "vectorized 1 loops" 1
    FAIL: gcc.dg/vect/vect-bitfield-write-3.c scan-tree-dump-times vect
    "vectorized 1 loops" 1
    
    As discussed in the PR, they require vect_long_long support, but fail
    to require that.
    
    This patch fixes this.
    
    Tested on sparc-sun-solaris2.11 and i386-pc-solaris2.11.
    
    2023-01-20  Rainer Orth  <ro@CeBiTec.Uni-Bielefeld.DE>
    
            gcc/testsuite:
            PR testsuite/107808
            * gcc.dg/vect/vect-bitfield-write-2.c: Require vect_long_long.
            * gcc.dg/vect/vect-bitfield-write-3.c: Likewise.

Diff:
---
 gcc/testsuite/gcc.dg/vect/vect-bitfield-write-2.c | 1 +
 gcc/testsuite/gcc.dg/vect/vect-bitfield-write-3.c | 1 +
 2 files changed, 2 insertions(+)

diff --git a/gcc/testsuite/gcc.dg/vect/vect-bitfield-write-2.c b/gcc/testsuite/gcc.dg/vect/vect-bitfield-write-2.c
index d550dd35ab7..1a101357ccc 100644
--- a/gcc/testsuite/gcc.dg/vect/vect-bitfield-write-2.c
+++ b/gcc/testsuite/gcc.dg/vect/vect-bitfield-write-2.c
@@ -1,4 +1,5 @@
 /* { dg-require-effective-target vect_int } */
+/* { dg-require-effective-target vect_long_long } */
 
 #include <stdarg.h>
 #include "tree-vect.h"
diff --git a/gcc/testsuite/gcc.dg/vect/vect-bitfield-write-3.c b/gcc/testsuite/gcc.dg/vect/vect-bitfield-write-3.c
index 3303d2610ff..5dc679627d5 100644
--- a/gcc/testsuite/gcc.dg/vect/vect-bitfield-write-3.c
+++ b/gcc/testsuite/gcc.dg/vect/vect-bitfield-write-3.c
@@ -1,4 +1,5 @@
 /* { dg-require-effective-target vect_int } */
+/* { dg-require-effective-target vect_long_long } */
 
 #include <stdarg.h>
 #include "tree-vect.h"

                 reply	other threads:[~2023-01-24  7:50 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=20230124075010.6F4D63858D33@sourceware.org \
    --to=ro@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).