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 target/98177] [11 Regression] SVE: ICE in expand_direct_optab_fn, at internal-fn.c:3368
Date: Fri, 18 Dec 2020 18:21:45 +0000	[thread overview]
Message-ID: <bug-98177-4-WwF3hX8wX6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98177-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:d44d47b49267b4265cee16d25b3f89dbf967cc0c

commit r11-6262-gd44d47b49267b4265cee16d25b3f89dbf967cc0c
Author: Przemyslaw Wirkus <przemyslaw.wirkus@arm.com>
Date:   Fri Dec 18 18:18:57 2020 +0000

    aarch64: SVE: ICE in expand_direct_optab_fn [PR98177]

    Problem comes from using the wrong interface to get the index type for a
    COND_REDUCTION. For fixed-length SVE we get a V2SI (a 64-bit Advanced
    SIMD vector) instead of a VNx2SI (an SVE vector that stores SI elements
    in DI containers).

    Credits to Richard Sandiford for pointing out the issue's root cause.

    Original PR snippet proposed to reproduce issue was only causing ICE for
C++
    compiler (see pr98177-1 test cases). I've slightly modified original
    snippet in order to reproduce issue on both C and C++ compilers. These
    are pr98177-2 test cases.

    gcc/ChangeLog:

            PR target/98177
            * tree-vect-loop.c (vect_create_epilog_for_reduction): Use
            get_same_sized_vectype to obtain index type.
            (vectorizable_reduction): Likewise.

    gcc/testsuite/ChangeLog:

            PR target/98177
            * g++.target/aarch64/sve/pr98177-1.C: New test.
            * g++.target/aarch64/sve/pr98177-2.C: New test.
            * gcc.target/aarch64/sve/pr98177-1.c: New test.
            * gcc.target/aarch64/sve/pr98177-2.c: New test.

  parent reply	other threads:[~2020-12-18 18:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-07 15:21 [Bug target/98177] New: " acoplan at gcc dot gnu.org
2020-12-07 15:21 ` [Bug target/98177] " acoplan at gcc dot gnu.org
2020-12-07 17:22 ` ktkachov at gcc dot gnu.org
2020-12-08  7:10 ` rguenth at gcc dot gnu.org
2020-12-18 18:21 ` cvs-commit at gcc dot gnu.org [this message]
2021-01-04  9:53 ` wirkus 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-98177-4-WwF3hX8wX6@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).