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/108272] [13 Regression] ICE in gen_movxo, at config/rs6000/mma.md:339
Date: Mon, 13 Feb 2023 02:18:50 +0000	[thread overview]
Message-ID: <bug-108272-4-jyG3J3FcGz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108272-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

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

commit r10-11211-gec4d91aa885297c3b5bb4bbfb3133ffe2e5e6a2f
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Sun Feb 12 09:35:27 2023 -0600

    rs6000: Teach rs6000_opaque_type_invalid_use_p about inline asm [PR108272]

    As PR108272 shows, there are some invalid uses of MMA opaque
    types in inline asm statements.  This patch is to teach the
    function rs6000_opaque_type_invalid_use_p for inline asm,
    check and error any invalid use of MMA opaque types in input
    and output operands.

            PR target/108272

    gcc/ChangeLog:

            * config/rs6000/rs6000.c (rs6000_opaque_type_invalid_use_p): Add
the
            support for invalid uses in inline asm, factor out the checking and
            erroring to lambda function check_and_error_invalid_use.

    gcc/testsuite/ChangeLog:

            * gcc.target/powerpc/pr108272-1.c: New test.
            * gcc.target/powerpc/pr108272-2.c: New test.
            * gcc.target/powerpc/pr108272-3.c: New test.
            * gcc.target/powerpc/pr108272-4.c: New test.

    (cherry picked from commit 074b0c03eabeb8e9c8de813c81bf87a1f88fdb65)

  parent reply	other threads:[~2023-02-13  2:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03  6:55 [Bug target/108272] New: " asolokha at gmx dot com
2023-01-03  7:04 ` [Bug target/108272] " linkw at gcc dot gnu.org
2023-01-05  6:53 ` linkw at gcc dot gnu.org
2023-01-09 18:42 ` asolokha at gmx dot com
2023-01-10  2:06 ` linkw at gcc dot gnu.org
2023-01-10  3:00 ` asolokha at gmx dot com
2023-01-16  8:17 ` cvs-commit at gcc dot gnu.org
2023-02-13  2:03 ` cvs-commit at gcc dot gnu.org
2023-02-13  2:09 ` cvs-commit at gcc dot gnu.org
2023-02-13  2:18 ` cvs-commit at gcc dot gnu.org [this message]
2023-02-13  2:25 ` linkw 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-108272-4-jyG3J3FcGz@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).