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/102327] gcc/config/i386/i386-expand.c:14678: Suspicious coding ?
Date: Wed, 15 Sep 2021 10:49:04 +0000	[thread overview]
Message-ID: <bug-102327-4-8tusd9oUbv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102327-4@http.gcc.gnu.org/bugzilla/>

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

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

commit r12-3547-g7fc4d6000a0d6c847c4c07373fbd4a17e54c678f
Author: liuhongt <hongtao.liu@intel.com>
Date:   Wed Sep 15 15:19:28 2021 +0800

    Optimize for V{8,16,32}HFmode vec_set/extract/init.

    gcc/ChangeLog:

            PR target/102327
            * config/i386/i386-expand.c
            (ix86_expand_vector_init_interleave): Use puncklwd to pack 2
            HFmodes.
            (ix86_expand_vector_set): Use blendw instead of pinsrw.
            * config/i386/i386.c (ix86_can_change_mode_class): Adjust for
            AVX512FP16 which supports 16bit vector load.
            * config/i386/sse.md (avx512bw_interleave_highv32hi<mask_name>):
            Rename to ..
            (avx512bw_interleave_high<mode><mask_name>): .. this, and
            extend to V32HFmode.
            (avx2_interleave_highv16hi<mask_name>): Rename to ..
            (avx2_interleave_high<mode><mask_name>): .. this, and extend
            to V16HFmode.
            (vec_interleave_highv8hi<mask_name>): Rename to ..
            (vec_interleave_high<mode><mask_name>): .. this, and extend to
V8HFmode.
            (<mask_codefor>avx512bw_interleave_lowv32hi<mask_name>):
            Rename to ..
            (<mask_codefor>avx512bw_interleave_low<mode><mask_name>):
            this, and extend to V32HFmode.
            (avx2_interleave_lowv16hi<mask_name>): Rename to ..
            (avx2_interleave_low<mode><mask_name>): .. this, and extend to
V16HFmode.
            (vec_interleave_lowv8hi<mask_name>): Rename to ..
            (vec_interleave_low<mode><mask_name>): .. this, and extend to
V8HFmode.
            (sse4_1_pblendw): Rename to ..
            (sse4_1_pblend<blendsuf>): .. this, and extend to V8HFmode.
            (avx2_pblendph): New define_expand.
            (<sse2p4_1>_pinsr<ssemodesuffix>): Refactor, use
            sseintmodesuffix instead of ssemodesuffix.
            (blendsuf): New mode attr.

    gcc/testsuite/ChangeLog:

            * gcc.target/i386/pr102327-1.c: New test.
            * gcc.target/i386/pr102327-2.c: New test.
            * gcc.target/i386/avx512fp16-1c.c: Adjust testcase.

  parent reply	other threads:[~2021-09-15 10:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-14 15:00 [Bug target/102327] New: " dcb314 at hotmail dot com
2021-09-14 15:01 ` [Bug target/102327] " dcb314 at hotmail dot com
2021-09-14 16:05 ` hjl.tools at gmail dot com
2021-09-15  1:10 ` crazylht at gmail dot com
2021-09-15  9:26 ` crazylht at gmail dot com
2021-09-15 10:49 ` cvs-commit at gcc dot gnu.org [this message]
2021-09-15 10:49 ` crazylht at gmail dot com
2021-09-15 20:39 ` pinskia 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-102327-4-8tusd9oUbv@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).