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/95960] New: GCC should re-vectorize vector code with larger VF Date: Mon, 29 Jun 2020 12:09:28 +0000 [thread overview] Message-ID: <bug-95960-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95960 Bug ID: 95960 Summary: GCC should re-vectorize vector code with larger VF Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: rguenth at gcc dot gnu.org Target Milestone: --- For the following simple case GCC should vectorize it using AVX: typedef double __attribute__((vector_size(16))) v2df; double a[4]; double b[4]; void f() { *(v2df *)&b[0] += *(v2df *)&a[0]; *(v2df *)&b[2] += *(v2df *)&a[2]; } Similar opportunities may exist for loops where also Neon -> SVE transforms may be profitable. Starting with BB vectorization might be easier since you only need to consider SLP.
next reply other threads:[~2020-06-29 12:09 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-29 12:09 rguenth at gcc dot gnu.org [this message] 2020-06-29 12:12 ` [Bug tree-optimization/95960] " rguenth at gcc dot gnu.org 2021-08-16 21:36 ` pinskia at gcc dot gnu.org 2024-01-26 5:55 ` pinskia 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-95960-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).