public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/106019] New: Surprising SLP failure on trivial code Date: Fri, 17 Jun 2022 17:51:00 +0000 [thread overview] Message-ID: <bug-106019-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106019 Bug ID: 106019 Summary: Surprising SLP failure on trivial code Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: amonakov at gcc dot gnu.org Target Milestone: --- In the following code, 'f' is not SLP-vectorized, but 'g' is. From a brief look at slp2 dump, looks like dependence analysis for p[i] vs. p[i+1] fails? void f(double *p, long i) { p[i+0] += 1; p[i+1] += 1; } void g(double *p, long i) { double *q = p + i; q[0] += 1; q[1] += 1; }
next reply other threads:[~2022-06-17 17:51 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-17 17:51 amonakov at gcc dot gnu.org [this message] 2022-06-20 8:10 ` [Bug tree-optimization/106019] " marxin at gcc dot gnu.org 2022-06-20 11:18 ` rguenth at gcc dot gnu.org 2022-06-20 16:40 ` rsandifo at gcc dot gnu.org 2022-06-21 6:48 ` rguenth at gcc dot gnu.org 2022-06-22 10:28 ` cvs-commit at gcc dot gnu.org 2022-06-22 10:29 ` rsandifo 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-106019-4@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).