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 middle-end/106016] [PowerPC] crash with attempt to initialize array of MMA accumulators
Date: Fri, 12 Aug 2022 02:09:58 +0000	[thread overview]
Message-ID: <bug-106016-4-GyK0Waz56D@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106016-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:df8567535a1f3eaa20b700be62374b2fb4f09204

commit r11-10201-gdf8567535a1f3eaa20b700be62374b2fb4f09204
Author: Peter Bergner <bergner@linux.ibm.com>
Date:   Fri Jun 17 23:43:23 2022 -0500

    c: Handle initializations of opaque types [PR106016]

    The initial commit that added opaque types thought that there couldn't
    be any valid initializations for variables of these types, but the test
    case in the bug report shows that isn't true.  The solution is to handle
    OPAQUE_TYPE initializations like the other scalar types.

    2022-06-17  Peter Bergner  <bergner@linux.ibm.com>

    gcc/
            PR c/106016
            * expr.c (count_type_elements): Handle OPAQUE_TYPE.

    gcc/testsuite/
            PR c/106016
            * gcc.target/powerpc/pr106016.c: New test.

    (cherry picked from commit 975658b782f36dcf6eb190966d5b705977bfd5eb)

  parent reply	other threads:[~2022-08-12  2:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 14:29 [Bug c/106016] New: " nemanja.i.ibm at gmail dot com
2022-06-17 17:19 ` [Bug target/106016] " segher at gcc dot gnu.org
2022-06-17 17:33 ` bergner at gcc dot gnu.org
2022-06-17 17:39 ` segher at gcc dot gnu.org
2022-06-17 19:30 ` bergner at gcc dot gnu.org
2022-06-17 19:37 ` bergner at gcc dot gnu.org
2022-06-17 19:53 ` segher at gcc dot gnu.org
2022-06-17 21:51 ` bergner at gcc dot gnu.org
2022-06-18  0:15 ` bergner at gcc dot gnu.org
2022-06-18  4:33 ` [Bug c/106016] " bergner at gcc dot gnu.org
2022-06-20 18:46 ` [Bug middle-end/106016] " segher at gcc dot gnu.org
2022-07-26 15:05 ` cvs-commit at gcc dot gnu.org
2022-08-12  0:26 ` cvs-commit at gcc dot gnu.org
2022-08-12  2:09 ` cvs-commit at gcc dot gnu.org [this message]
2022-08-12  2:12 ` 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-106016-4-GyK0Waz56D@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).