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/110485] vectorizing simd clone calls without loop masking applied
Date: Thu, 19 Oct 2023 17:31:03 +0000	[thread overview]
Message-ID: <bug-110485-4-bKQ5lYnFhh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110485-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andre Simoes Dias Vieira
<avieira@gcc.gnu.org>:

https://gcc.gnu.org/g:8b704ed0b8f35ec1a57e70bd8e6913ba0e9d1f24

commit r14-4765-g8b704ed0b8f35ec1a57e70bd8e6913ba0e9d1f24
Author: Andre Vieira <andre.simoesdiasvieira@arm.com>
Date:   Thu Oct 19 18:28:12 2023 +0100

    vect: don't allow fully masked loops with non-masked simd clones [PR
110485]

    When analyzing a loop and choosing a simdclone to use it is possible to
choose
    a simdclone that cannot be used 'inbranch' for a loop that can use partial
    vectors.  This may lead to the vectorizer deciding to use partial vectors
which
    are not supported for notinbranch simd clones.  This patch fixes that by
    disabling the use of partial vectors once a notinbranch simd clone has been
    selected.

    gcc/ChangeLog:

            PR tree-optimization/110485
            * tree-vect-stmts.cc (vectorizable_simd_clone_call): Disable
partial
            vectors usage if a notinbranch simdclone has been selected.

    gcc/testsuite/ChangeLog:

            * gcc.dg/gomp/pr110485.c: New test.

  parent reply	other threads:[~2023-10-19 17:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29 12:21 [Bug tree-optimization/110485] New: " rguenth at gcc dot gnu.org
2023-07-02 21:10 ` [Bug tree-optimization/110485] " rsandifo at gcc dot gnu.org
2023-07-03  8:52 ` rguenth at gcc dot gnu.org
2023-10-19 17:31 ` cvs-commit at gcc dot gnu.org [this message]
2023-12-05 14:25 ` rguenth 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-110485-4-bKQ5lYnFhh@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).