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/100310] [AVX512] Missing support for v{,p}expand* instructions that w/o mask operands
Date: Tue, 22 Jun 2021 01:35:37 +0000	[thread overview]
Message-ID: <bug-100310-4-PIvAJUHQZ2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100310-4@http.gcc.gnu.org/bugzilla/>

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

--- 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:b6efffa552cee6a20a58c91e5f41466c5715d73d

commit r12-1705-gb6efffa552cee6a20a58c91e5f41466c5715d73d
Author: liuhongt <hongtao.liu@intel.com>
Date:   Wed Apr 28 14:52:59 2021 +0800

    Fix ICE for vpexpand*.

    gcc/ChangeLog

            PR target/100310
            * config/i386/i386-expand.c
            (ix86_expand_special_args_builtin): Keep constm1_operand only
            if it satisfies insn's operand predicate.

    gcc/testsuite/ChangeLog

            PR target/100310
            * gcc.target/i386/pr100310.c: New test.

  parent reply	other threads:[~2021-06-22  1:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28  8:35 [Bug target/100310] New: " crazylht at gmail dot com
2021-05-07  2:22 ` [Bug target/100310] " crazylht at gmail dot com
2021-05-25  1:11 ` crazylht at gmail dot com
2021-06-22  1:35 ` cvs-commit at gcc dot gnu.org [this message]
2021-06-22  1:41 ` cvs-commit at gcc dot gnu.org
2021-06-22  1:48 ` crazylht at gmail dot com

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-100310-4-PIvAJUHQZ2@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).