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/100645] ICE in related_vector_mode, at stor-layout.c:537
Date: Wed, 19 Oct 2022 09:05:18 +0000	[thread overview]
Message-ID: <bug-100645-4-KJaflQkDrb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100645-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:6db4ba9750ffd65c80995425db0d5f1020a04b28

commit r12-8845-g6db4ba9750ffd65c80995425db0d5f1020a04b28
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Sun Sep 25 22:01:50 2022 -0500

    rs6000: Fix condition of define_expand vec_shr_<mode> [PR100645]

    PR100645 exposes one latent bug in define_expand vec_shr_<mode>
    that the current condition TARGET_ALTIVEC is too loose.  The
    mode iterator VEC_L contains a few modes, they are not always
    supported as vector mode, VECTOR_UNIT_ALTIVEC_OR_VSX_P should
    be used like some other VEC_L usages.

            PR target/100645

    gcc/ChangeLog:

            * config/rs6000/vector.md (vec_shr_<mode>): Replace condition
            TARGET_ALTIVEC with VECTOR_UNIT_ALTIVEC_OR_VSX_P.

    gcc/testsuite/ChangeLog:

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

    (cherry picked from commit bfad7069b74c97000b698191c1945f07a6192db5)

  parent reply	other threads:[~2022-10-19  9:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18  2:59 [Bug rtl-optimization/100645] New: " asolokha at gmx dot com
2022-09-14  1:03 ` [Bug target/100645] " linkw at gcc dot gnu.org
2022-09-14  8:23 ` linkw at gcc dot gnu.org
2022-09-26  3:24 ` cvs-commit at gcc dot gnu.org
2022-10-19  9:05 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-19  9:08 ` 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-100645-4-KJaflQkDrb@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).