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/106017] [PowerPC] No array-to-pointer conversion for MMA accumulator
Date: Mon, 29 Aug 2022 22:38:31 +0000	[thread overview]
Message-ID: <bug-106017-4-KA2apr6ApX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106017-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Peter Bergner
<bergner@gcc.gnu.org>:

https://gcc.gnu.org/g:22ff125247ff5328ad4544aef939d491618d714d

commit r12-8726-g22ff125247ff5328ad4544aef939d491618d714d
Author: Peter Bergner <bergner@linux.ibm.com>
Date:   Sat Aug 27 19:44:16 2022 -0500

    rs6000: Allow conversions of MMA pointer types [PR106017]

    GCC incorrectly disables conversions between MMA pointer types, which
    are allowed with clang.  The original intent was to disable conversions
    between MMA types and other other types, but pointer conversions should
    have been allowed.  The fix is to just remove the MMA pointer conversion
    handling code altogether.

    gcc/
            PR target/106017
            * config/rs6000/rs6000.cc (rs6000_invalid_conversion): Remove
handling
            of MMA pointer conversions.

    gcc/testsuite/
            PR target/106017
            * gcc.target/powerpc/pr106017.c: New test.

    (cherry picked from commit 1ae1325f24cea1698b56e4299d95446a1f7b90a2)

  parent reply	other threads:[~2022-08-29 22:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 14:34 [Bug c/106017] New: " nemanja.i.ibm at gmail dot com
2022-06-17 17:16 ` [Bug target/106017] " segher at gcc dot gnu.org
2022-06-17 17:31 ` bergner at gcc dot gnu.org
2022-06-17 17:35 ` segher at gcc dot gnu.org
2022-06-17 19:19 ` nemanja.i.ibm at gmail dot com
2022-06-17 19:51 ` segher at gcc dot gnu.org
2022-06-17 20:50 ` segher at gcc dot gnu.org
2022-06-17 22:23 ` bergner at gcc dot gnu.org
2022-08-27 17:28 ` bergner at gcc dot gnu.org
2022-08-27 17:30 ` bergner at gcc dot gnu.org
2022-08-27 18:27 ` bergner at gcc dot gnu.org
2022-08-28  0:44 ` cvs-commit at gcc dot gnu.org
2022-08-29 22:38 ` cvs-commit at gcc dot gnu.org [this message]
2022-08-30  0:22 ` cvs-commit at gcc dot gnu.org
2022-08-30  1:13 ` cvs-commit at gcc dot gnu.org
2022-08-30  1:14 ` 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-106017-4-KA2apr6ApX@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).