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/110776] [14 Regression] powerpc-darwin bootstrap broken after r14-2490 with ICE rs6000.cc:5069 building libgfortran
Date: Thu, 27 Jul 2023 02:43:58 +0000	[thread overview]
Message-ID: <bug-110776-4-AaVxVotnZl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110776-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

https://gcc.gnu.org/g:9890d4e8bcda1f34b8eefb481935ef0e4cd8069e

commit r14-2813-g9890d4e8bcda1f34b8eefb481935ef0e4cd8069e
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Wed Jul 26 21:43:09 2023 -0500

    vect: Treat VMAT_ELEMENTWISE as scalar load in costing [PR110776]

    PR110776 exposes one issue that we could query unaligned
    load for vector type but actually no unaligned vector load
    is supported there.  The reason is that the costed load is
    with single-lane vector type and its memory access type is
    VMAT_ELEMENTWISE, we actually take it as scalar load and
    set its alignment_support_scheme as dr_unaligned_supported.

    To avoid the ICE as exposed, following Rich's suggestion,
    this patch is to make VMAT_ELEMENTWISE be costed as scalar
    load.

    Co-authored-by: Richard Biener <rguenther@suse.de>

            PR tree-optimization/110776

    gcc/ChangeLog:

            * tree-vect-stmts.cc (vectorizable_load): Always cost
VMAT_ELEMENTWISE
            as scalar load.

    gcc/testsuite/ChangeLog:

            * gcc.target/powerpc/pr110776.c: New test.

  parent reply	other threads:[~2023-07-27  2:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-22 15:45 [Bug target/110776] New: " iains at gcc dot gnu.org
2023-07-22 15:48 ` [Bug target/110776] " iains at gcc dot gnu.org
2023-07-22 16:07 ` pinskia at gcc dot gnu.org
2023-07-24  1:49 ` linkw at gcc dot gnu.org
2023-07-25  2:52 ` linkw at gcc dot gnu.org
2023-07-25  2:54 ` linkw at gcc dot gnu.org
2023-07-25  6:34 ` rguenther at suse dot de
2023-07-25  6:53 ` linkw at gcc dot gnu.org
2023-07-25 11:05 ` rguenther at suse dot de
2023-07-25 19:44 ` iains at gcc dot gnu.org
2023-07-26  2:54 ` linkw at gcc dot gnu.org
2023-07-27  2:43 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-27  2:45 ` linkw 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-110776-4-AaVxVotnZl@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).