public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/98772] Widening patterns causing missed vectorization
Date: Thu, 11 Feb 2021 15:05:35 +0000	[thread overview]
Message-ID: <bug-98772-4-9IDHCXH3JP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98772-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Joel Hutton <joelh@gcc.gnu.org>:

https://gcc.gnu.org/g:4af29981ab57ad7ef4467e371e4145cce9c16eaa

commit r11-7189-g4af29981ab57ad7ef4467e371e4145cce9c16eaa
Author: Joel Hutton <joel.hutton@arm.com>
Date:   Thu Feb 11 14:59:26 2021 +0000

    [aarch64][vect] Support V8QI->V8HI WIDEN_ patterns

    In the case where 8 out of every 16 elements are widened using a
    widening pattern and the next 8 are skipped, the patterns are not
    recognized. This is because they are normally used in a pair, such  as
    VEC_WIDEN_MINUS_HI/LO, to achieve a v16qi->v16hi conversion for example.
    This patch adds support for V8QI->V8HI patterns.

    gcc/ChangeLog:

            PR tree-optimization/98772
            * optabs-tree.c (supportable_half_widening_operation): New function
            to check for supportable V8QI->V8HI widening patterns.
            * optabs-tree.h (supportable_half_widening_operation): New
function.
            * tree-vect-stmts.c (vect_create_half_widening_stmts): New function
            to create promotion stmts for V8QI->V8HI widening patterns.
            (vectorizable_conversion): Add case for V8QI->V8HI.

    gcc/testsuite/ChangeLog:

            PR tree-optimization/98772
            * gcc.target/aarch64/pr98772.c: New test.

  parent reply	other threads:[~2021-02-11 15:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20 15:26 [Bug tree-optimization/98772] New: " joelh at gcc dot gnu.org
2021-01-20 15:36 ` [Bug tree-optimization/98772] " rguenth at gcc dot gnu.org
2021-01-21 11:13 ` joelh at gcc dot gnu.org
2021-01-21 13:18 ` rguenth at gcc dot gnu.org
2021-01-21 15:30 ` rsandifo at gcc dot gnu.org
2021-02-11 15:05 ` cvs-commit at gcc dot gnu.org [this message]
2021-02-11 15:07 ` joelh 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-98772-4-9IDHCXH3JP@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).