public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/100267] gcc -O2 for avx512 instrincts generates extra warnings and less optimizations
Date: Wed, 28 Apr 2021 08:52:41 +0000	[thread overview]
Message-ID: <bug-100267-4-vO9DEyokSs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100267-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Hongtao.liu <crazylht at gmail dot com> ---
After support v{,p}expand* thats w/o mask operands, codegen seems to be optimal

dummyf1_avx512x8:
.LFB5668:
        .cfi_startproc
        movl    (%rdi), %edx
        movq    8(%rdi), %rax
        vmovdqu (%rax,%rdx,8), %ymm0
        vmovdqu 32(%rax,%rdx,8), %ymm1
        vpexpandq       %ymm0, %ymm0
        vpexpandq       %ymm1, %ymm1
        vpaddq  %ymm1, %ymm0, %ymm0
        ret
        .cfi_endproc

  parent reply	other threads:[~2021-04-28  8:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26 12:48 [Bug middle-end/100267] New: " konstantin.ananyev at intel dot com
2021-04-27  7:08 ` [Bug middle-end/100267] " rguenth at gcc dot gnu.org
2021-04-27 12:07 ` crazylht at gmail dot com
2021-04-28  8:52 ` crazylht at gmail dot com [this message]
2021-04-28  9:56 ` crazylht at gmail dot com
2021-04-30  1:13 ` crazylht at gmail dot com
2021-05-07  2:22 ` crazylht at gmail dot com
2021-06-22  1:35 ` cvs-commit at gcc dot gnu.org
2021-06-22  1:47 ` 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-100267-4-vO9DEyokSs@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).