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/109508] [13 Regression] ICE: in extract_insn, at recog.cc:2791 with -mcpu=sifive-s76 on riscv64
Date: Sun, 16 Apr 2023 15:56:40 +0000	[thread overview]
Message-ID: <bug-109508-4-eCOAUOmAg4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109508-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jeff Law <law@gcc.gnu.org>:

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

commit r13-7198-ga647198fcf7463a42c8e035a429200e7998735dc
Author: Jeff Law <jlaw@ventanamicro>
Date:   Sun Apr 16 09:55:32 2023 -0600

    [committed] [PR target/109508] Adjust conditional move expansion for SFB

    Recently the conditional move expander's predicates were loosened for the
    benefit of the THEAD processors.  In particular one operand that was
    previously "register_operand" is now "reg_or_0_operand".  That's fine for
    THEAD, but breaks for SFB which requires a register for that operand.

    This results in an ICE when compiling the testcase an SFB target such as
    the sifive s76.

    This change adjusts the expansion code slightly to copy the value into
    a register for SFB.

    Bootstrapped and regression tested (c,c++,fortran only) with a toolchain
    configured to enable SFB by default.

            PR target/109508
    gcc/

            * config/riscv/riscv.cc (riscv_expand_conditional_move): For
            TARGET_SFB_ALU, force the true arm into a register.

    gcc/testsuite
            * gcc.target/riscv/pr109508.c: New test.

  parent reply	other threads:[~2023-04-16 15:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-14  4:50 [Bug target/109508] New: " zsojka at seznam dot cz
2023-04-14  4:59 ` [Bug target/109508] " law at gcc dot gnu.org
2023-04-14  5:09 ` law at gcc dot gnu.org
2023-04-14  7:41 ` rguenth at gcc dot gnu.org
2023-04-14  7:41 ` rguenth at gcc dot gnu.org
2023-04-16 15:56 ` cvs-commit at gcc dot gnu.org [this message]
2023-04-16 15:57 ` law 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-109508-4-eCOAUOmAg4@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).