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/105587] [13 Regression] ICE in extract_insn, at recog.cc:2791 (error: unrecognizable insn) since r13-210-gfcda0efccad41eba
Date: Mon, 16 May 2022 00:30:51 +0000	[thread overview]
Message-ID: <bug-105587-4-DrDeRjykDv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105587-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 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:69c4b5c519f0df37e4903992644cc29682721bc1

commit r13-468-g69c4b5c519f0df37e4903992644cc29682721bc1
Author: liuhongt <hongtao.liu@intel.com>
Date:   Fri May 13 15:48:01 2022 +0800

    Fix ICE caused by wrong condition.

    When d->perm[i] == d->perm[i-1] + 1 and d->perm[i] == nelt, it's not
    continuous. It should fail if there's more than 2 continuous areas.

    gcc/ChangeLog:

            PR target/105587
            * config/i386/i386-expand.cc
            (expand_vec_perm_pslldq_psrldq_por): Fail when (d->perm[i] ==
            d->perm[i-1] + 1) && d->perm[i] == nelt && start != -1.

    gcc/testsuite/ChangeLog:

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

  parent reply	other threads:[~2022-05-16  0:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12 22:44 [Bug tree-optimization/105587] New: [13 Regression] ICE in extract_insn, at recog.cc:2791 (error: unrecognizable insn) vsevolod.livinskiy at gmail dot com
2022-05-13  6:14 ` [Bug tree-optimization/105587] [13 Regression] ICE in extract_insn, at recog.cc:2791 (error: unrecognizable insn) since r13-210-gfcda0efccad41eba marxin at gcc dot gnu.org
2022-05-13  6:22 ` [Bug target/105587] " pinskia at gcc dot gnu.org
2022-05-13  7:55 ` rguenth at gcc dot gnu.org
2022-05-13  7:58 ` crazylht at gmail dot com
2022-05-16  0:30 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-16  0:43 ` crazylht at gmail dot com
2022-05-18 16:35 ` slyfox at gcc dot gnu.org
2022-09-13 18:50 ` asolokha at gmx dot com
2022-09-13 19:20 ` 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-105587-4-DrDeRjykDv@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).