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/109735] [14 Regression] ICE in vectorizable_store, at tree-vect-stmts.cc:8529 since r14-322-g821ef93976e750
Date: Fri, 05 May 2023 12:19:15 +0000	[thread overview]
Message-ID: <bug-109735-4-xdzkwByx44@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109735-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:37b5f031292fbdb854ee791de3883362cf2afcff

commit r14-494-g37b5f031292fbdb854ee791de3883362cf2afcff
Author: Richard Biener <rguenther@suse.de>
Date:   Fri May 5 08:54:28 2023 +0200

    tree-optimization/109735 - conversion for vectorized pointer-diff

    There's handling in vectorizable_operation for POINTER_DIFF_EXPR
    requiring conversion of the result of the unsigned operation to
    a signed type.  But that's conditional on the "default" kind of
    vectorization.  In this PR it's shown the emulated vector path
    needs it and I think the masked operation case will, too (though
    we might eventually never mask an integral MINUS_EXPR).  So the
    following makes that handling unconditional.

            PR tree-optimization/109735
            * tree-vect-stmts.cc (vectorizable_operation): Perform
            conversion for POINTER_DIFF_EXPR unconditionally.

  parent reply	other threads:[~2023-05-05 12:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04 14:06 [Bug tree-optimization/109735] New: " marxin at gcc dot gnu.org
2023-05-04 14:06 ` [Bug tree-optimization/109735] " marxin at gcc dot gnu.org
2023-05-05  6:16 ` rguenth at gcc dot gnu.org
2023-05-05  6:54 ` rguenth at gcc dot gnu.org
2023-05-05 12:19 ` cvs-commit at gcc dot gnu.org [this message]
2023-05-05 12:19 ` 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-109735-4-xdzkwByx44@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).