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/104188] [11/12 Regression] gcc omitting AVX-512 broadcast instruction
Date: Mon, 24 Jan 2022 00:43:33 +0000	[thread overview]
Message-ID: <bug-104188-4-KU3Wa1JJ9g@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104188-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by H.J. Lu <hjl@gcc.gnu.org>:

https://gcc.gnu.org/g:4d2321314a656dd3e30117e2a5266cbacb1e60eb

commit r12-6831-g4d2321314a656dd3e30117e2a5266cbacb1e60eb
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Sat Jan 22 12:04:30 2022 -0800

    x86: Also check mode of memory broadcast in bcst_mem_operand

    Return false for invalid mode on memory broadcast in bcst_mem_operand:

    (vec_duplicate:V16SF (mem/j:V4SF (reg/v/f:DI 109 [ b ])))

    gcc/

            PR target/104188
            * config/i386/predicates.md (bcst_mem_operand): Also check mode
            of memory broadcast.

    gcc/testsuite/

            PR target/104188
            * gcc.target/i386/pr104188.c: New test.

  parent reply	other threads:[~2022-01-24  0:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-22 17:03 [Bug target/104188] New: " kvr000 at gmail dot com
2022-01-22 17:40 ` [Bug target/104188] " pinskia at gcc dot gnu.org
2022-01-22 17:49 ` kvr000 at gmail dot com
2022-01-22 17:55 ` jakub at gcc dot gnu.org
2022-01-22 18:36 ` kvr000 at gmail dot com
2022-01-22 18:50 ` jakub at gcc dot gnu.org
2022-01-22 19:00 ` [Bug target/104188] [11/12 Regression] " jakub at gcc dot gnu.org
2022-01-22 19:23 ` hjl.tools at gmail dot com
2022-01-22 19:51 ` hjl.tools at gmail dot com
2022-01-22 22:25 ` hjl.tools at gmail dot com
2022-01-22 23:29 ` kvr000 at gmail dot com
2022-01-23 18:37 ` hjl.tools at gmail dot com
2022-01-24  0:43 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-24  0:47 ` cvs-commit at gcc dot gnu.org
2022-01-24  0:48 ` hjl.tools at gmail dot com
2022-01-26 11:00 ` cvs-commit at gcc dot gnu.org
2022-01-26 11:07 ` 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-104188-4-KU3Wa1JJ9g@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).