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/96506] ICE when using an MMA type as a function param
Date: Wed, 19 Aug 2020 02:42:04 +0000 [thread overview]
Message-ID: <bug-96506-4-FeWy0IJwAP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96506-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96506
--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Peter Bergner
<bergner@gcc.gnu.org>:
https://gcc.gnu.org/g:43edad43b2cee17fb7575c40a9dafac3fe79ba1c
commit r10-8641-g43edad43b2cee17fb7575c40a9dafac3fe79ba1c
Author: Peter Bergner <bergner@linux.ibm.com>
Date: Thu Aug 13 13:40:39 2020 -0500
rs6000: ICE when using an MMA type as a function param or return value
[PR96506]
PR96506 shows a problem where we ICE on illegal usage, namely using MMA
types for function arguments and return values. The solution is to flag
these illegal usages as errors early, before we ICE.
2020-08-13 Peter Bergner <bergner@linux.ibm.com>
gcc/
PR target/96506
* config/rs6000/rs6000-call.c (rs6000_promote_function_mode):
Disallow
MMA types as return values.
(rs6000_function_arg): Disallow MMA types as function arguments.
gcc/testsuite/
PR target/96506
* gcc.target/powerpc/pr96506.c: New test.
(cherry picked from commit 0ad7e730c142ef6cd0ddc1491a89a7f330caa887)
next prev parent reply other threads:[~2020-08-19 2:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 16:15 [Bug target/96506] New: " bergner at gcc dot gnu.org
2020-08-06 16:17 ` [Bug target/96506] " bergner at gcc dot gnu.org
2020-08-13 18:43 ` cvs-commit at gcc dot gnu.org
2020-08-19 2:42 ` cvs-commit at gcc dot gnu.org [this message]
2020-08-19 2:55 ` 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-96506-4-FeWy0IJwAP@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).