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/107934] ICE: SIGSEGV in immediate_operand (recog.cc:1618) with -O2 -mtune=knl -ffinite-math-only and __bf16 since r13-4314-ga1ecc5600464f6a6
Date: Fri, 02 Dec 2022 01:29:22 +0000	[thread overview]
Message-ID: <bug-107934-4-gBUcEsht5y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107934-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by hongtao Liu <liuhongt@gcc.gnu.org>:

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

commit r13-4454-ge055e6db974d8b8950b30859a853e0aee74e20c2
Author: liuhongt <hongtao.liu@intel.com>
Date:   Thu Dec 1 11:41:49 2022 +0800

    Fix ICE due to incorrect insn type.

    ;; if reg/mem op
    (define_insn_reservation  "slm_sseishft_3" 2
      (and (eq_attr "cpu" "slm")
           (and (eq_attr "type" "sseishft")
                (not (match_operand 2 "immediate_operand"))))
      "slm-complex, slm-all-eu")

    in slm.md it will check operands[2] for type sseishft, but for
    extendbfsf2_1 there's no second operand which caused ICE.
    The patch set type from sseishft to sseishft1 to fix the issue.

    gcc/ChangeLog:

            PR target/107934
            * config/i386/i386.md (extendbfsf2_1): Change type from
            sseishft to sseishft1.

    gcc/testsuite/ChangeLog:

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

  parent reply	other threads:[~2022-12-02  1:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30 14:02 [Bug target/107934] New: ICE: SIGSEGV in immediate_operand (recog.cc:1618) with -O2 -mtune=knl -ffinite-math-only and __bf16 zsojka at seznam dot cz
2022-11-30 14:05 ` [Bug target/107934] ICE: SIGSEGV in immediate_operand (recog.cc:1618) with -O2 -mtune=knl -ffinite-math-only and __bf16 since r13-4314-ga1ecc5600464f6a6 marxin at gcc dot gnu.org
2022-11-30 14:21 ` ubizjak at gmail dot com
2022-12-01  1:45 ` crazylht at gmail dot com
2022-12-02  1:29 ` cvs-commit at gcc dot gnu.org [this message]
2022-12-02  1:29 ` crazylht at gmail dot com
2022-12-02  9:44 ` marxin 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-107934-4-gBUcEsht5y@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).