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)] Allow bigger SLP graphs Date: Thu, 2 Nov 2023 13:59:30 +0000 (GMT) [thread overview] Message-ID: <20231102135930.9B30838582A3@sourceware.org> (raw) https://gcc.gnu.org/g:4a2309e2599ee0dce49187ad89d90bf373950ee3 commit 4a2309e2599ee0dce49187ad89d90bf373950ee3 Author: Richard Biener <rguenther@suse.de> Date: Fri Sep 29 13:05:01 2023 +0200 Allow bigger SLP graphs When doing single-lane SLP discovery only we're easily running into the SLP graph size limit when patterns are involved. The following ups the limit from the number of scalar stmts to the number of scalar or pattern stmts by using the number of stmt_vec_infos created. * tree-vect-loop.cc (vect_analyze_loop_2): Use the number of stmt_vec_infos created to limit the SLP graph size. Diff: --- gcc/tree-vect-loop.cc | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/gcc/tree-vect-loop.cc b/gcc/tree-vect-loop.cc index 3b28c826b3b9..77215a175a3e 100644 --- a/gcc/tree-vect-loop.cc +++ b/gcc/tree-vect-loop.cc @@ -2813,8 +2813,10 @@ vect_analyze_loop_2 (loop_vec_info loop_vinfo, bool &fatal, if (slp) { /* Check the SLP opportunities in the loop, analyze and build - SLP trees. */ - ok = vect_analyze_slp (loop_vinfo, LOOP_VINFO_N_STMTS (loop_vinfo)); + SLP trees. Use the number of stmt_vec_infos as graph limit + since that also includes pattern stmts which LOOP_VINFO_N_STMTS + does not. */ + ok = vect_analyze_slp (loop_vinfo, loop_vinfo->stmt_vec_infos.length ()); if (!ok) return ok;
next reply other threads:[~2023-11-02 13:59 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-02 13:59 Richard Biener [this message] -- strict thread matches above, loose matches on Subject: below -- 2024-05-13 14:27 Richard Biener 2024-02-23 7:31 Richard Biener 2023-11-09 13:03 Richard Biener 2023-10-19 13:29 Richard Biener 2023-10-16 12:49 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=20231102135930.9B30838582A3@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: linkBe 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).