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/101322] ICE in copy_to_mode_reg, at explow.c:651
Date: Thu, 01 Sep 2022 02:17:17 +0000 [thread overview]
Message-ID: <bug-101322-4-dgllt5I33U@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101322-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101322
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Peter Bergner <bergner@gcc.gnu.org>:
https://gcc.gnu.org/g:2985049049f12b0aa3366ca244d387820385b9e8
commit r13-2331-g2985049049f12b0aa3366ca244d387820385b9e8
Author: Peter Bergner <bergner@linux.ibm.com>
Date: Wed Aug 31 21:14:36 2022 -0500
rs6000: Don't ICE when we disassemble an MMA variable [PR101322]
When we expand an MMA disassemble built-in with C++ using a pointer that
is cast to a valid MMA type, the type isn't passed down to the expand
machinery and we end up using the base type of the pointer which leads to
an ICE. This patch enforces we always use the correct MMA type regardless
of the pointer type being used.
2022-08-31 Peter Bergner <bergner@linux.ibm.com>
gcc/
PR target/101322
* config/rs6000/rs6000-builtin.cc (rs6000_gimple_fold_mma_builtin):
Enforce the use of a valid MMA pointer type.
gcc/testsuite/
PR target/101322
* g++.target/powerpc/pr101322.C: New test.
next prev parent reply other threads:[~2022-09-01 2:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-101322-4@http.gcc.gnu.org/bugzilla/>
2022-08-26 19:15 ` bergner at gcc dot gnu.org
2022-09-01 2:17 ` cvs-commit at gcc dot gnu.org [this message]
2022-09-03 1:50 ` cvs-commit at gcc dot gnu.org
2022-09-12 17:40 ` cvs-commit at gcc dot gnu.org
2022-09-13 22:26 ` cvs-commit at gcc dot gnu.org
2022-09-13 22:27 ` bergner 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-101322-4-dgllt5I33U@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).