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/104502] [12 Regression] ICE: in extract_constrain_insn, at recog.cc:2670: insn does not satisfy its constraints with -O -flive-range-shrinkage -march=barcelona -fstack-protector-all -mavx512f
Date: Tue, 10 May 2022 08:23:47 +0000	[thread overview]
Message-ID: <bug-104502-4-0SjWAhNO6O@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104502-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 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:b49c185ca5d44b03c4e374a81d7c9ea82fed2bfd

commit r10-10678-gb49c185ca5d44b03c4e374a81d7c9ea82fed2bfd
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Sat Feb 12 11:17:41 2022 +0100

    i386: Fix up cvtsd2ss splitter [PR104502]

    The following testcase ICEs, because AVX512F is enabled, AVX512VL is not,
    and the cvtsd2ss insn has %xmm0-15 as output operand and %xmm16-31 as
    input operand.  For output operand %xmm16+ the splitter just gives up
    in such case, but for such input it just emits vmovddup which requires
    AVX512VL if either operand is EXT_REX_SSE_REG_P (when it is 128-bit).

    The following patch fixes it by treating that case like the pre-SSE3
    output != input case - move the input to output and do everything on
    the output reg which is known to be < %xmm16.

    2022-02-12  Jakub Jelinek  <jakub@redhat.com>

            PR target/104502
            * config/i386/i386.md (cvtsd2ss splitter): If operands[1] is xmm16+
            and AVX512VL isn't available, move operands[1] to operands[0]
first.

            * gcc.target/i386/pr104502.c: New test.

    (cherry picked from commit 0538d42cdd68f6b65d72ed7768f1d00ba44f8631)

  parent reply	other threads:[~2022-05-10  8:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11 14:51 [Bug target/104502] New: " zsojka at seznam dot cz
2022-02-11 15:02 ` [Bug target/104502] " jakub at gcc dot gnu.org
2022-02-11 15:39 ` jakub at gcc dot gnu.org
2022-02-12 10:18 ` cvs-commit at gcc dot gnu.org
2022-02-12 10:22 ` jakub at gcc dot gnu.org
2022-02-19  8:02 ` cvs-commit at gcc dot gnu.org
2022-05-10  8:23 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-11  6:24 ` cvs-commit 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-104502-4-0SjWAhNO6O@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).