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/94398] ICE: in vectorizable_load, at tree-vect-stmts.c:9173
Date: Tue, 31 Mar 2020 14:14:03 +0000	[thread overview]
Message-ID: <bug-94398-4-vLw2lMgzhm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94398-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 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:f14b41d27124601284347a10d496362c8b4b8e1c

commit r10-7481-gf14b41d27124601284347a10d496362c8b4b8e1c
Author: Felix Yang <felix.yang@huawei.com>
Date:   Tue Mar 31 16:41:56 2020 +0800

    vect: ICE: in vectorizable_load, at tree-vect-stmts.c:9173 [PR94398]

    In the testcase for PR94398, we're trying to compute:

      alignment_support_scheme
        = vect_supportable_dr_alignment (first_dr_info, false);
      gcc_assert (alignment_support_scheme);

    even for VMAT_GATHER_SCATTER, which always accesses individual elements.
    Here we should set alignment_support_scheme to dr_unaligned_supported
    the gather/scatter case instead of calling vect_supportable_dr_alignment.

    2020-03-31  Felix Yang  <felix.yang@huawei.com>

    gcc/
            PR tree-optimization/94398
            * tree-vect-stmts.c (vectorizable_store): Instead of calling
            vect_supportable_dr_alignment, set alignment_support_scheme to
            dr_unaligned_supported for gather-scatter accesses.
            (vectorizable_load): Likewise.

    gcc/testsuite/
            PR tree-optimization/94398
            * gcc.target/aarch64/pr94398.c: New test.

  parent reply	other threads:[~2020-03-31 14:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-30  9:22 [Bug tree-optimization/94398] New: " z.zhanghaijian at huawei dot com
2020-03-30  9:23 ` [Bug tree-optimization/94398] " z.zhanghaijian at huawei dot com
2020-03-30  9:31 ` rguenth at gcc dot gnu.org
2020-03-30  9:55 ` rsandifo at gcc dot gnu.org
2020-03-30  9:56 ` rsandifo at gcc dot gnu.org
2020-03-31 14:14 ` cvs-commit at gcc dot gnu.org [this message]
2021-11-29  8:45 ` pinskia 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-94398-4-vLw2lMgzhm@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).