public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/97678] [11 regression] execution fail for gcc.target/powerpc/p9-vec-length-epil-run-5.c after r11-4614 Date: Tue, 03 Nov 2020 08:34:45 +0000 [thread overview] Message-ID: <bug-97678-4-0RFAjLFzVU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97678-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97678 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- Ah, the vectorized epilogue is wrong since we do not represent the initial value there correctly. We still have the {0, 0} invariant in the corresponding SLP tree. Hmm. So previously we're relying on the actual PHI node(s) preheader value plus eventually honoring LOOP_VINFO_MASK_SKIP_NITERS.
next prev parent reply other threads:[~2020-11-03 8:34 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-02 18:44 [Bug tree-optimization/97678] New: " seurer at gcc dot gnu.org 2020-11-03 7:20 ` [Bug tree-optimization/97678] " rguenth at gcc dot gnu.org 2020-11-03 7:51 ` rguenth at gcc dot gnu.org 2020-11-03 8:34 ` rguenth at gcc dot gnu.org [this message] 2020-11-03 10:13 ` cvs-commit at gcc dot gnu.org 2020-11-03 10:20 ` rguenth 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-97678-4-0RFAjLFzVU@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).