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 middle-end/106030] [13 Regression] ice in emit_move_insn, at expr.cc:4026
Date: Wed, 03 May 2023 15:18:37 +0000	[thread overview]
Message-ID: <bug-106030-4-TxwXTuP0Wd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106030-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:89741783f6e7127d4d8be5a5e8e4fb7d5785f8a6

commit r10-11332-g89741783f6e7127d4d8be5a5e8e4fb7d5785f8a6
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Tue Jun 21 11:38:59 2022 +0200

    expand: Fix up expand_cond_expr_using_cmove [PR106030]

    If expand_cond_expr_using_cmove can't find a cmove optab for a particular
    mode, it tries to promote the mode and perform the cmove in the promoted
    mode.

    The testcase in the patch ICEs on arm because in that case we pass temp
which
    has the promoted mode (SImode) as target to expand_operands where the
    operands have the non-promoted mode (QImode).
    Later on the function uses paradoxical subregs:
      if (GET_MODE (op1) != mode)
        op1 = gen_lowpart (mode, op1);

      if (GET_MODE (op2) != mode)
        op2 = gen_lowpart (mode, op2);
    to change the operand modes.

    The following patch fixes it by passing NULL_RTX as target if it has
    promoted mode.

    2022-06-21  Jakub Jelinek  <jakub@redhat.com>

            PR middle-end/106030
            * expr.c (expand_cond_expr_using_cmove): Pass NULL_RTX instead of
            temp to expand_operands if mode has been promoted.

            * gcc.c-torture/compile/pr106030.c: New test.

    (cherry picked from commit 2df1df945fac85d7b3d084001414a66a2709d8fe)

      parent reply	other threads:[~2023-05-03 15:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-19 16:02 [Bug c/106030] New: " dcb314 at hotmail dot com
2022-06-19 16:08 ` [Bug c/106030] " dcb314 at hotmail dot com
2022-06-20 12:11 ` [Bug target/106030] " jakub at gcc dot gnu.org
2022-06-20 12:11 ` [Bug middle-end/106030] " jakub at gcc dot gnu.org
2022-06-20 12:52 ` jakub at gcc dot gnu.org
2022-06-20 14:32 ` acoplan at gcc dot gnu.org
2022-06-20 14:34 ` [Bug middle-end/106030] [13 Regression] " jakub at gcc dot gnu.org
2022-06-20 14:34 ` jakub at gcc dot gnu.org
2022-06-20 14:49 ` dcb314 at hotmail dot com
2022-06-21  9:39 ` cvs-commit at gcc dot gnu.org
2022-06-28 15:38 ` cvs-commit at gcc dot gnu.org
2022-06-28 15:48 ` jakub at gcc dot gnu.org
2022-11-04  8:30 ` cvs-commit at gcc dot gnu.org
2023-05-03 15:18 ` cvs-commit at gcc dot gnu.org [this message]

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-106030-4-TxwXTuP0Wd@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).