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/103702] [12 Regression] ICE in update_target_cost_per_stmt, at config/rs6000/rs6000.c:5457
Date: Thu, 27 Jan 2022 11:16:44 +0000	[thread overview]
Message-ID: <bug-103702-4-BcTOXl5PwJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103702-4@http.gcc.gnu.org/bugzilla/>

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

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

commit r12-6891-g2022be54daf638885e1e685afd36619cb4b01a93
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Thu Jan 27 03:46:28 2022 -0600

    rs6000: Fix an assertion in update_target_cost_per_stmt [PR103702]

    This patch is to fix one wrong assertion which is too aggressive.
    Vectorizer can do vec_construct costing for the vector type which
    only has one unit.  For the failed case, the passed in vector type
    is "vector(1) int", though it doesn't end up with any construction
    eventually, we have to handle this kind of possibility.

    gcc/ChangeLog:

            PR target/103702
            * config/rs6000/rs6000.cc
            (rs6000_cost_data::update_target_cost_per_stmt): Fix one wrong
            assertion with early return.

    gcc/testsuite/ChangeLog:

            PR target/103702
            * gcc.target/powerpc/pr103702.c: New test.

  parent reply	other threads:[~2022-01-27 11:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-14  4:42 [Bug target/103702] New: " asolokha at gmx dot com
2021-12-14  8:50 ` [Bug target/103702] " linkw at gcc dot gnu.org
2021-12-14  9:04 ` linkw at gcc dot gnu.org
2022-01-03 10:20 ` rguenth at gcc dot gnu.org
2022-01-17 12:44 ` rguenth at gcc dot gnu.org
2022-01-18  1:39 ` linkw at gcc dot gnu.org
2022-01-27 11:16 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-27 11:20 ` 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-103702-4-BcTOXl5PwJ@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).