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)] Reduce single-lane SLP testresult noise
Date: Fri, 23 Feb 2024 07:31:45 +0000 (GMT)	[thread overview]
Message-ID: <20240223073145.D7C93385843B@sourceware.org> (raw)

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

commit a373df9da828ad09aff6f7bab46e5330c9b299ff
Author: Richard Biener <rguenther@suse.de>
Date:   Thu Oct 5 13:31:16 2023 +0200

    Reduce single-lane SLP testresult noise
    
    The following avoids dumping 'vectorizing stmts using SLP' for
    single-lane instances since that causes extra testsuite fallout.
    
            * tree-vect-slp.cc (vect_schedule_slp): Gate dumping
            'vectorizing stmts using SLP' on > 1 lanes.

Diff:
---
 gcc/tree-vect-slp.cc | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/gcc/tree-vect-slp.cc b/gcc/tree-vect-slp.cc
index a9236179e261..83ee8a7efc32 100644
--- a/gcc/tree-vect-slp.cc
+++ b/gcc/tree-vect-slp.cc
@@ -9985,7 +9985,8 @@ vect_schedule_slp (vec_info *vinfo, const vec<slp_instance> &slp_instances)
       if (!SLP_INSTANCE_ROOT_STMTS (instance).is_empty ())
 	vectorize_slp_instance_root_stmt (node, instance);
 
-      if (dump_enabled_p ())
+      /* ???  Reduce some testsuite noise because of "more SLP".  */
+      if (SLP_TREE_LANES (node) > 1 && dump_enabled_p ())
 	dump_printf_loc (MSG_NOTE, vect_location,
                          "vectorizing stmts using SLP.\n");
     }

             reply	other threads:[~2024-02-23  7:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-23  7:31 Richard Biener [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-13 14:27 Richard Biener
2023-11-09 13:03 Richard Biener
2023-11-02 13:59 Richard Biener
2023-10-19 13:29 Richard Biener
2023-10-16 12:50 Richard Biener
2023-10-06  7:07 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=20240223073145.D7C93385843B@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).