public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "stammark at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/108177] MVE predicated stores to same address get optimized away Date: Thu, 06 Apr 2023 17:32:22 +0000 [thread overview] Message-ID: <bug-108177-4-zl2vkFCz4z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108177-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108177 --- Comment #5 from Stam Markianos-Wright <stammark at gcc dot gnu.org> --- With the fix to MVE auto_inc having gone in as ddc9b5ee13cd686c8674f92d46045563c06a23ea I have found that this fix keeps the auto-inc on these predicated stores broken. It seems to fail in auto_inc_dec at this condition: ``` /* Make sure this reg appears only once in this insn. */ if (count_occurrences (PATTERN (mem_insn.insn), mem_insn.reg0, 1) != 1) { if (dump_file) fprintf (dump_file, "mem count failure\n"); return false; } ``` (which makes sense with the pattern now having the MEM appear twice) I guess this is not urgent since this is only a performance impact on one instruction. Also if the change needs to be in the auto-inc pass instead of the backend, then likely something for GCC14, but I thought this would be a good place to record this ;) Does anyone have any ideas on this? Or I wonder what the AVX case does for this
next prev parent reply other threads:[~2023-04-06 17:32 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-19 14:29 [Bug target/108177] New: " avieira at gcc dot gnu.org 2022-12-19 14:30 ` [Bug target/108177] " avieira at gcc dot gnu.org 2022-12-19 15:47 ` rguenth at gcc dot gnu.org 2022-12-19 17:20 ` avieira at gcc dot gnu.org 2023-01-24 17:02 ` cvs-commit at gcc dot gnu.org 2023-04-06 17:32 ` stammark at gcc dot gnu.org [this message] 2023-05-18 10:43 ` 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-108177-4-zl2vkFCz4z@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).