public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-8443] testsuite/vect: Fix pr25413a.c expectations [PR109705]
Date: Fri, 26 Jan 2024 07:35:01 +0000 (GMT)	[thread overview]
Message-ID: <20240126073501.5E5123858CD1@sourceware.org> (raw)

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

commit r14-8443-gbfd6b36f08021f023e0e9223f5aea315b74a5c56
Author: Andrew Pinski <quic_apinski@quicinc.com>
Date:   Thu Jan 25 13:58:10 2024 -0800

    testsuite/vect: Fix pr25413a.c expectations [PR109705]
    
    The 2 loops in octfapg_universe can and will be vectorized now
    after r14-333-g6d4b59a9356ac4 on targets that support multiplication
    in the long type. But the testcase does not check vect_long_mult for
    that, so this patch corrects that error and now the testcase passes correctly
    on aarch64-linux-gnu (with and without SVE).
    
    Built and tested on aarch64-linux-gnu (with and without SVE).
    
    gcc/testsuite/ChangeLog:
    
            PR testsuite/109705
            * gcc.dg/vect/pr25413a.c: Expect 1 vectorized loops for !vect_long_mult
            and 2 for vect_long_mult.
    
    Signed-off-by: Andrew Pinski <quic_apinski@quicinc.com>

Diff:
---
 gcc/testsuite/gcc.dg/vect/pr25413a.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.dg/vect/pr25413a.c b/gcc/testsuite/gcc.dg/vect/pr25413a.c
index ffb517c9ce06..905665e5dbe8 100644
--- a/gcc/testsuite/gcc.dg/vect/pr25413a.c
+++ b/gcc/testsuite/gcc.dg/vect/pr25413a.c
@@ -123,6 +123,8 @@ int main (void)
   return 0;
 } 
 
-/* { dg-final { scan-tree-dump-times "vectorized 2 loops" 1 "vect" } } */
+/* The second loop in octfapg_universe requires long multiply to do the vectorization. */
+/* { dg-final { scan-tree-dump-times "vectorized 1 loops" 1 "vect" { target { ! vect_long_mult } } } } */
+/* { dg-final { scan-tree-dump-times "vectorized 2 loops" 1 "vect" { target vect_long_mult  } } } */
 /* { dg-final { scan-tree-dump-times "vector alignment may not be reachable" 1 "vect" { target { ! vector_alignment_reachable  } } } } */
 /* { dg-final { scan-tree-dump-times "Alignment of access forced using versioning" 1 "vect" { target { ! vector_alignment_reachable } } } } */

                 reply	other threads:[~2024-01-26  7:35 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=20240126073501.5E5123858CD1@sourceware.org \
    --to=pinskia@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).