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/94683] ICE in forwprop when folding to a VEC_PERM_EXPR
Date: Tue, 21 Apr 2020 15:11:31 +0000	[thread overview]
Message-ID: <bug-94683-4-HSuCcVmClz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94683-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:85353e24ca90282e1d3620682841f524de20475c

commit r10-7851-g85353e24ca90282e1d3620682841f524de20475c
Author: Richard Sandiford <richard.sandiford@arm.com>
Date:   Tue Apr 21 16:11:07 2020 +0100

    forwprop: Fix ICE when building a VEC_PERM_EXPR [PR94683]

    The type compatibility handling in simplify_vector_constructor is
    based on the number of elements and on element type compatibility,
    but that's no longer enough to ensure that two vector types are
    compatible.  This patch uses a VIEW_CONVERT_EXPR if the permutation
    type and result type are distinct.

    2020-04-21  Richard Sandiford  <richard.sandiford@arm.com>

    gcc/
            PR tree-optimization/94683
            * tree-ssa-forwprop.c (simplify_vector_constructor): Use a
            VIEW_CONVERT_EXPR to handle mixtures of similarly-structured
            but distinct vector types.

    gcc/testsuite/
            PR tree-optimization/94683
            * gcc.target/aarch64/sve/acle/general/pr94683.c: New test.

  parent reply	other threads:[~2020-04-21 15:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21  9:03 [Bug tree-optimization/94683] New: " rsandifo at gcc dot gnu.org
2020-04-21  9:03 ` [Bug tree-optimization/94683] " rsandifo at gcc dot gnu.org
2020-04-21 15:11 ` cvs-commit at gcc dot gnu.org [this message]
2020-04-21 16:05 ` rsandifo 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-94683-4-HSuCcVmClz@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).