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/108752] New: word_mode vectorization is pessimized by hard limit on nunits
Date: Fri, 10 Feb 2023 11:24:30 +0000	[thread overview]
Message-ID: <bug-108752-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 108752
           Summary: word_mode vectorization is pessimized by hard limit on
                    nunits
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rguenth at gcc dot gnu.org
  Target Milestone: ---

r13-5771-gdc87e1391c55c6 re-introduced a hard nunits limit to the vectorizer
when using emulated vectors (aka word_mode vectorization).  That's because
this feature relies on vector lowering to implement plus, minus and negate
with bit operations and that has such limit in place for when dealing with
user written code that didn't have any cost modeling applied.

The fix is to emit supported operations from the vectorizer.

             reply	other threads:[~2023-02-10 11:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10 11:24 rguenth at gcc dot gnu.org [this message]
2023-02-10 11:24 ` [Bug tree-optimization/108752] " rguenth at gcc dot gnu.org
2023-02-10 12:12 ` rguenth at gcc dot gnu.org
2023-02-12 23:49 ` hp at gcc dot gnu.org
2023-04-28  9:07 ` cvs-commit at gcc dot gnu.org
2023-04-28  9:08 ` rguenth at gcc dot gnu.org
2023-05-23 16:10 ` cvs-commit 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-108752-4@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).