public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106016] [PowerPC] crash with attempt to initialize array of MMA accumulators
Date: Sat, 18 Jun 2022 00:15:04 +0000 [thread overview]
Message-ID: <bug-106016-4-1ardtSPeM5@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 #8 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Peter Bergner from comment #7)
> (In reply to Segher Boessenkool from comment #6)
> > Like that yes. Pre-approved if it survives regcheck, too. Thanks!
> >
> > Please add the testcase as well of course :-)
>
> Ok, bootstrap and regtests are running.
Bootstrap and regression testing were clean.
next prev parent reply other threads:[~2022-06-18 0:15 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 [this message]
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
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-1ardtSPeM5@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).