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(refs/users/rguenth/heads/vect-force-slp)] PR60276 fix for single-lane SLP
Date: Thu,  9 Nov 2023 13:03:48 +0000 (GMT)	[thread overview]
Message-ID: <20231109130348.D08763856974@sourceware.org> (raw)

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

commit faece3c2dc2e952d1bc24818a15081113843c85e
Author: Richard Biener <rguenther@suse.de>
Date:   Thu Nov 9 11:30:22 2023 +0100

    PR60276 fix for single-lane SLP
    
    When enabling single-lane SLP and not splitting groups the fix for
    PR60276 is no longer effective since it for unknown reason exempted
    pure SLP.  The following removes this exemption, making
    gcc.dg/vect/pr60276.c PASS even with --param vect-single-lane-slp=1
    
            PR tree-optimization/60276
            * tree-vect-stmts.cc (vectorizable_load): Do not exempt
            pure_slp grouped loads from the STMT_VINFO_MIN_NEG_DIST
            restriction.

Diff:
---
 gcc/tree-vect-stmts.cc | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/gcc/tree-vect-stmts.cc b/gcc/tree-vect-stmts.cc
index ddbcb0c50dc..ceaf573ddfe 100644
--- a/gcc/tree-vect-stmts.cc
+++ b/gcc/tree-vect-stmts.cc
@@ -9922,8 +9922,7 @@ vectorizable_load (vec_info *vinfo,
 
       /* Invalidate assumptions made by dependence analysis when vectorization
 	 on the unrolled body effectively re-orders stmts.  */
-      if (!PURE_SLP_STMT (stmt_info)
-	  && STMT_VINFO_MIN_NEG_DIST (stmt_info) != 0
+      if (STMT_VINFO_MIN_NEG_DIST (stmt_info) != 0
 	  && maybe_gt (LOOP_VINFO_VECT_FACTOR (loop_vinfo),
 		       STMT_VINFO_MIN_NEG_DIST (stmt_info)))
 	{

             reply	other threads:[~2023-11-09 13:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-09 13:03 Richard Biener [this message]
2024-02-23  7:31 Richard Biener

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=20231109130348.D08763856974@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).