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/94962] Suboptimal AVX2 code for _mm256_zextsi128_si256(_mm_set1_epi8(-1)) Date: Mon, 18 May 2020 10:01:14 +0000 [thread overview] Message-ID: <bug-94962-4-OHyxcG87qA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94962-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94962 --- Comment #4 from Hongtao.liu <crazylht at gmail dot com> --- (In reply to Jakub Jelinek from comment #2) > But such an instruction isn't always redundant, it really depends on what > the previous setter of the register did, whether the upper 128 bit of the > 256-bit register are already guaranteed to be zero or not. ---- (define_insn "avx_vec_concat<mode>" [(set (match_operand:V_256_512 0 "register_operand" "=x,v,x,Yv") (vec_concat:V_256_512 (match_operand:<ssehalfvecmode> 1 "nonimmediate_operand" "x,v,xm,vm") (match_operand:<ssehalfvecmode> 2 "nonimm_or_0_operand" "xm,vm,C,C")))] define_insn "*<extract_type>_vinsert<shuffletype><extract_suf>_0" [(set (match_operand:AVX512_VEC 0 "register_operand" "=v,x,Yv") (vec_merge:AVX512_VEC (match_operand:AVX512_VEC 1 "reg_or_0_operand" "v,C,C") (vec_duplicate:AVX512_VEC (match_operand:<ssequartermode> 2 "nonimmediate_operand" "vm,xm,vm")) (match_operand:SI 3 "const_int_operand" "n,n,n")))] ---- Upper part already zeroed. > Thus the #c1 patch looks incorrect to me, one would need peephole2s or some > combine patterns or target specific pass etc. to discover that at least for > the common cases; and it isn't something we model in the RTL patterns (what > insns guarantee which upper bits zero and what do not; and for some there > can be different choices even in the same define_insn, we could implement > something using widened registers and then there would be no guarantee etc.).
next prev parent reply other threads:[~2020-05-18 10:01 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-05 21:41 [Bug tree-optimization/94962] New: " nemo@self-evident.org 2020-05-18 8:41 ` [Bug target/94962] " crazylht at gmail dot com 2020-05-18 9:37 ` jakub at gcc dot gnu.org 2020-05-18 9:55 ` crazylht at gmail dot com 2020-05-18 10:01 ` crazylht at gmail dot com [this message] 2020-05-18 15:43 ` nemo@self-evident.org 2020-05-19 6:14 ` crazylht at gmail dot com 2020-05-19 16:39 ` nemo@self-evident.org 2022-09-23 5:29 ` cvs-commit at gcc dot gnu.org 2022-09-23 5:32 ` crazylht at gmail dot com 2022-09-26 5:30 ` 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-94962-4-OHyxcG87qA@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).