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 r15-18] disable ldist for test, to restore vectorizing-candidate loop
Date: Sun, 28 Apr 2024 07:42:13 +0000 (GMT)	[thread overview]
Message-ID: <20240428074213.1EE1F3858D33@sourceware.org> (raw)

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

commit r15-18-gcc6a439fdab933963b00c488e221ae33d7199aeb
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Sun Apr 28 04:30:15 2024 -0300

    disable ldist for test, to restore vectorizing-candidate loop
    
    The loop we're supposed to try to vectorize in
    gcc.dg/vect/costmodel/ppc/costmodel-vect-31a.c is turned into a memset
    before the vectorizer runs.
    
    Various other tests in this set have already run into this, and the
    solution has been to disable this loop distribution transformation,
    enabled at -O2, so that the vectorizer gets a chance to transform the
    loop and, in this testcase, fail to do so.
    
    
    for  gcc/testsuite/ChangeLog
    
            * gcc.dg/vect/costmodel/ppc/costmodel-vect-31a.c: Disable
            ldist.

Diff:
---
 gcc/testsuite/gcc.dg/vect/costmodel/ppc/costmodel-vect-31a.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/gcc/testsuite/gcc.dg/vect/costmodel/ppc/costmodel-vect-31a.c b/gcc/testsuite/gcc.dg/vect/costmodel/ppc/costmodel-vect-31a.c
index 454a714a309..90b5d5a7f40 100644
--- a/gcc/testsuite/gcc.dg/vect/costmodel/ppc/costmodel-vect-31a.c
+++ b/gcc/testsuite/gcc.dg/vect/costmodel/ppc/costmodel-vect-31a.c
@@ -1,4 +1,5 @@
 /* { dg-require-effective-target vect_int } */
+/* { dg-additional-options "-fno-tree-loop-distribute-patterns" } */
 
 #include <stdarg.h>
 #include "../../tree-vect.h"

                 reply	other threads:[~2024-04-28  7:42 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=20240428074213.1EE1F3858D33@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).