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/109244] internal compiler error: in setup_preferred_alternate_classes_for_new_pseudos, at ira.cc:2892
Date: Thu, 23 Mar 2023 03:22:54 +0000	[thread overview]
Message-ID: <bug-109244-4-exMIlAHwJy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109244-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kito Cheng <kito@gcc.gnu.org>:

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

commit r13-6823-gcd0c433e5faba9a18f64881cd761a53a530aa798
Author: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
Date:   Wed Mar 22 10:49:56 2023 +0800

    RISC-V: Fix LRA issue for LMUL < 1 vector spillings [PR109244]

    In order to decrease the memory traffic, we don't use whole register
    load/store for the LMUL less than 1 and mask mode, so those case will
    require one extra general purpose register for setting up VL register,
    but it's not allowed during LRA process, so we defined few special move
patterns
    used for LRA, which will defer the expansion after LRA.

    gcc/ChangeLog:

            PR target/109244
            * config/riscv/riscv-protos.h (emit_vlmax_vsetvl): Define as
global.
            (emit_vlmax_op): Ditto.
            * config/riscv/riscv-v.cc (get_sew): New function.
            (emit_vlmax_vsetvl): Adapt function.
            (emit_pred_op): Ditto.
            (emit_vlmax_op): Ditto.
            (emit_nonvlmax_op): Ditto.
            (legitimize_move): Fix LRA ICE.
            (gen_no_side_effects_vsetvl_rtx): Adapt function.
            * config/riscv/vector.md (@mov<V_FRACT:mode><P:mode>_lra): New
pattern.
            (@mov<VB:mode><P:mode>_lra): Ditto.
            (*mov<V_FRACT:mode><P:mode>_lra): Ditto.
            (*mov<VB:mode><P:mode>_lra): Ditto.

    gcc/testsuite/ChangeLog:

            PR target/109244
            * g++.target/riscv/rvv/base/pr109244.C: New test.
            * gcc.target/riscv/rvv/base/binop_vv_constraint-4.c: Adapt
testcase.
            * gcc.target/riscv/rvv/base/binop_vv_constraint-6.c: Ditto.
            * gcc.target/riscv/rvv/base/binop_vx_constraint-127.c: Ditto.
            * gcc.target/riscv/rvv/base/spill-1.c: Ditto.
            * gcc.target/riscv/rvv/base/spill-2.c: Ditto.
            * gcc.target/riscv/rvv/base/spill-3.c: Ditto.
            * gcc.target/riscv/rvv/base/spill-5.c: Ditto.
            * gcc.target/riscv/rvv/base/spill-7.c: Ditto.
            * g++.target/riscv/rvv/base/bug-18.C: New test.
            * gcc.target/riscv/rvv/base/merge_constraint-3.c: New test.
            * gcc.target/riscv/rvv/base/merge_constraint-4.c: New test.

  parent reply	other threads:[~2023-03-23  3:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22  7:22 [Bug c++/109244] New: " malat at debian dot org
2023-03-22  7:41 ` [Bug target/109244] " juzhe.zhong at rivai dot ai
2023-03-22  7:50 ` malat at debian dot org
2023-03-22  8:03 ` juzhe.zhong at rivai dot ai
2023-03-23  1:51 ` kito at gcc dot gnu.org
2023-03-23  3:22 ` cvs-commit at gcc dot gnu.org [this message]
2023-03-23  3:23 ` kito 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-109244-4-exMIlAHwJy@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).