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 target/101579] Suboptimal codegen for __builtin_shufflevector Date: Wed, 28 Jul 2021 09:01:12 +0000 [thread overview] Message-ID: <bug-101579-4-8DN6QsBNbc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101579-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101579 --- Comment #3 from Hongtao.liu <crazylht at gmail dot com> --- Codegen could be improved by -mavx512bw, but still not good as clang12
next prev parent reply other threads:[~2021-07-28 9:01 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-22 12:41 [Bug target/101579] New: " hjl.tools at gmail dot com 2021-07-27 10:14 ` [Bug target/101579] " rguenth at gcc dot gnu.org 2021-07-27 10:35 ` jakub at gcc dot gnu.org 2021-07-28 9:01 ` crazylht at gmail dot com [this message] 2021-07-28 9:40 ` crazylht at gmail dot com 2021-07-28 9:45 ` crazylht at gmail dot com 2021-07-28 9:49 ` jakub at gcc dot gnu.org 2021-07-28 10:03 ` crazylht at gmail dot com 2021-07-28 10:12 ` 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-101579-4-8DN6QsBNbc@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: linkBe 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).