public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/95960] GCC should re-vectorize vector code with larger VF
Date: Mon, 29 Jun 2020 12:12:48 +0000	[thread overview]
Message-ID: <bug-95960-4-2lC42IqPUS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95960-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95960

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 48801
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48801&action=edit
start

So quick experiments show where we need to do adjustments.  We do have
an explicit SLP_TREE_LANES we could use for "true" scalar lanes as compared
to the number of "scalar" stmts but uses might have been transitioned not
exactly along this boundary.  Then there's of course 'group_size' which
can mean either depending on context.

The biggest churn is likely in dataref group analysis where we IMHO
also want a "lanes" representation.

  reply	other threads:[~2020-06-29 12:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 12:09 [Bug tree-optimization/95960] New: " rguenth at gcc dot gnu.org
2020-06-29 12:12 ` rguenth at gcc dot gnu.org [this message]
2021-08-16 21:36 ` [Bug tree-optimization/95960] " pinskia at gcc dot gnu.org
2024-01-26  5:55 ` pinskia at gcc dot gnu.org

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=bug-95960-4-2lC42IqPUS@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).