public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/aoliva/heads/testme)] adjust vectorization expectations for ppc costmodel 76b
Date: Mon, 22 Apr 2024 05:13:14 +0000 (GMT)	[thread overview]
Message-ID: <20240422051314.7D9A93858401@sourceware.org> (raw)

https://gcc.gnu.org/g:9b0c52b69c85acbceccc5676509cfc0fbb41dd52

commit 9b0c52b69c85acbceccc5676509cfc0fbb41dd52
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Sun Apr 21 17:24:18 2024 -0300

    adjust vectorization expectations for ppc costmodel 76b
    
    This test expects vectorization at power8+ because strict alignment is
    not required for vectors.  For power7, vectorization is not to take
    place because it's not deemed profitable: 12 iterations would be
    required to make it so.
    
    But for power6 and below, the test's 10 iterations are enough to make
    vectorization profitable, but the test doesn't expect this.  Assuming
    the decision is indeed appropriate, I'm adjusting the expectations.
    
    
    for  gcc/testsuite/ChangeLog
    
            * gcc.dg/vect/costmodel/ppc/costmodel-vect-76b.c: Adjust
            expectations for cpus below power7.

Diff:
---
 gcc/testsuite/gcc.dg/vect/costmodel/ppc/costmodel-vect-76b.c | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/gcc/testsuite/gcc.dg/vect/costmodel/ppc/costmodel-vect-76b.c b/gcc/testsuite/gcc.dg/vect/costmodel/ppc/costmodel-vect-76b.c
index cbbfbb24658..0dab2c08acd 100644
--- a/gcc/testsuite/gcc.dg/vect/costmodel/ppc/costmodel-vect-76b.c
+++ b/gcc/testsuite/gcc.dg/vect/costmodel/ppc/costmodel-vect-76b.c
@@ -46,9 +46,10 @@ int main (void)
   return 0;
 }
 
-/* Peeling to align the store is used. Overhead of peeling is too high.  */
-/* { dg-final { scan-tree-dump-times "vectorized 1 loops" 0 "vect" { target { vector_alignment_reachable && {! vect_no_align} } } } } */
-/* { dg-final { scan-tree-dump-times "vectorization not profitable" 1 "vect" { target { vector_alignment_reachable && {! vect_hw_misalign} } } } } */
+/* Peeling to align the store is used. Overhead of peeling is too high
+   for power7, but acceptable for earlier architectures.  */
+/* { dg-final { scan-tree-dump-times "vectorized 1 loops" 0 "vect" { target { has_arch_pwr7 && { vector_alignment_reachable && {! vect_no_align} } } } } } */
+/* { dg-final { scan-tree-dump-times "vectorization not profitable" 1 "vect" { target { has_arch_pwr7 && { vector_alignment_reachable && {! vect_hw_misalign} } } } } } */
 
 /* Versioning to align the store is used. Overhead of versioning is not too high.  */
-/* { dg-final { scan-tree-dump-times "vectorized 1 loops" 1 "vect" { target { vect_no_align || {! vector_alignment_reachable} } } } } */
+/* { dg-final { scan-tree-dump-times "vectorized 1 loops" 1 "vect" { target { vect_no_align || { {! vector_alignment_reachable} || {! has_arch_pwr7 } } } } } } */

             reply	other threads:[~2024-04-22  5:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22  5:13 Alexandre Oliva [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-22  6:56 Alexandre Oliva
2024-04-21 20:27 Alexandre Oliva
2023-04-06  6:34 Alexandre Oliva
2023-03-30 14:06 Alexandre Oliva
2023-03-24  6:24 Alexandre Oliva
2023-03-23  3:47 Alexandre Oliva
2023-03-16 14:21 Alexandre Oliva
2023-03-15 14:05 Alexandre Oliva
2021-03-11 10:21 Alexandre Oliva
2021-03-09 21:47 Alexandre Oliva
2021-03-09 21:25 Alexandre Oliva
2021-03-09  2:26 Alexandre Oliva

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=20240422051314.7D9A93858401@sourceware.org \
    --to=aoliva@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).