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 rtl-optimization/110202] _mm512_ternarylogic_epi64 generates unnecessary operations Date: Wed, 12 Jul 2023 07:51:46 +0000 [thread overview] Message-ID: <bug-110202-4-Jq2zIurFLp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110202-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110202 --- Comment #10 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:13c556d6ae84be3ee2bc245a56eafa58221de86a commit r14-2447-g13c556d6ae84be3ee2bc245a56eafa58221de86a Author: liuhongt <hongtao.liu@intel.com> Date: Thu Jun 29 14:25:28 2023 +0800 Break false dependence for vpternlog by inserting vpxor or setting constraint of input operand to '0' False dependency happens when destination is only updated by pternlog. There is no false dependency when destination is also used in source. So either a pxor should be inserted, or input operand should be set with constraint '0'. gcc/ChangeLog: PR target/110438 PR target/110202 * config/i386/predicates.md (int_float_vector_all_ones_operand): New predicate. * config/i386/sse.md (*vmov<mode>_constm1_pternlog_false_dep): New define_insn. (*<avx512>_cvtmask2<ssemodesuffix><mode>_pternlog_false_dep): Ditto. (*<avx512>_cvtmask2<ssemodesuffix><mode>_pternlog_false_dep): Ditto. (*<avx512>_cvtmask2<ssemodesuffix><mode>): Adjust to define_insn_and_split to avoid false dependence. (*<avx512>_cvtmask2<ssemodesuffix><mode>): Ditto. (<mask_codefor>one_cmpl<mode>2<mask_name>): Adjust constraint of operands 1 to '0' to avoid false dependence. (*andnot<mode>3): Ditto. (iornot<mode>3): Ditto. (*<nlogic><mode>3): Ditto. gcc/testsuite/ChangeLog: * gcc.target/i386/pr110438.c: New test. * gcc.target/i386/pr100711-6.c: Adjust testcase.
next prev parent reply other threads:[~2023-07-12 7:51 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-10 10:37 [Bug c++/110202] New: " fabio at cannizzo dot net 2023-06-10 16:07 ` [Bug target/110202] " pinskia at gcc dot gnu.org 2023-06-10 16:14 ` [Bug rtl-optimization/110202] " pinskia at gcc dot gnu.org 2023-06-10 18:36 ` jakub at gcc dot gnu.org 2023-06-10 21:10 ` pinskia at gcc dot gnu.org 2023-06-12 17:14 ` fabio at cannizzo dot net 2023-06-12 19:04 ` amonakov at gcc dot gnu.org 2023-06-27 17:59 ` amonakov at gcc dot gnu.org 2023-06-28 0:47 ` crazylht at gmail dot com 2023-06-28 5:07 ` amonakov at gcc dot gnu.org 2023-07-12 7:51 ` cvs-commit at gcc dot gnu.org [this message] 2023-08-04 16:44 ` [Bug target/110202] " cvs-commit at gcc dot gnu.org 2023-08-05 15:32 ` amonakov 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-110202-4-Jq2zIurFLp@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).