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/112476] Unrecognizable insn with -O2 -march=la464 on loongarch64
Date: Mon, 13 Nov 2023 06:16:06 +0000	[thread overview]
Message-ID: <bug-112476-4-jqAR6QmA8h@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112476-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Xi Ruoyao <xry111@gcc.gnu.org>:

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

commit r14-5374-gb88500e0bc1e9e3a396ba764f9b701d22a76818f
Author: Xi Ruoyao <xry111@xry111.site>
Date:   Sun Nov 12 00:55:13 2023 +0800

    LoongArch: Use simplify_gen_subreg instead of gen_rtx_SUBREG in
loongarch_expand_vec_cond_mask_expr [PR112476]

    GCC internal says:

        'subreg's of 'subreg's are not supported.  Using
        'simplify_gen_subreg' is the recommended way to avoid this problem.

    Unfortunately loongarch_expand_vec_cond_mask_expr might create nested
    subreg under certain circumstances, causing an ICE.

    Use simplify_gen_subreg as the internal document suggests.

    gcc/ChangeLog:

            PR target/112476
            * config/loongarch/loongarch.cc
            (loongarch_expand_vec_cond_mask_expr): Call simplify_gen_subreg
            instead of gen_rtx_SUBREG.

    gcc/testsuite/ChangeLog:

            PR target/112476
            * gcc.target/loongarch/pr112476-1.c: New test.
            * gcc.target/loongarch/pr112476-2.c: New test.

  parent reply	other threads:[~2023-11-13  6:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-10 11:58 [Bug rtl-optimization/112476] New: [14 Regression] unrecognizable " xen0n at gentoo dot org
2023-11-10 13:41 ` [Bug rtl-optimization/112476] Unrecognizable " xry111 at gcc dot gnu.org
2023-11-11 10:32 ` xry111 at gcc dot gnu.org
2023-11-11 11:08 ` xry111 at gcc dot gnu.org
2023-11-11 16:49 ` [Bug target/112476] " xry111 at gcc dot gnu.org
2023-11-12  1:02 ` xry111 at gcc dot gnu.org
2023-11-13  6:16 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-13  6:22 ` xry111 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-112476-4-jqAR6QmA8h@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).