public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/104368] New: [12 Regression] Failure to vectorise conditional grouped accesses after PR102659 Date: Thu, 03 Feb 2022 14:51:41 +0000 [thread overview] Message-ID: <bug-104368-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104368 Bug ID: 104368 Summary: [12 Regression] Failure to vectorise conditional grouped accesses after PR102659 Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: enhancement Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: rsandifo at gcc dot gnu.org Target Milestone: --- The following test regressed with PR102659, compiled with -O3 -march=armv8.2-a+sve: void f(int *restrict x, int *restrict y, int n) { for (int i = 0; i < n; ++i) if (x[i] > 0) x[i] = y[i * 2] + y[i * 2 + 1]; } Previously we treated the y[] accesses as a linear group and so could use LD2W. Now we treat them as individual gather loads instead: .L3: ld1w z1.s, p0/z, [x0, x3, lsl 2] lsl z0.s, z2.s, #1 cmpgt p0.s, p0/z, z1.s, #0 ld1w z1.s, p0/z, [x1, z0.s, sxtw 2] // Gather ld1w z0.s, p0/z, [x5, z0.s, sxtw 2] // Gather add z0.s, z1.s, z0.s st1w z0.s, p0, [x0, x3, lsl 2] incw z2.s add x3, x3, x4 whilelo p0.s, w3, w2 b.any .L3
next reply other threads:[~2022-02-03 14:51 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-03 14:51 rsandifo at gcc dot gnu.org [this message] 2022-02-03 23:42 ` [Bug tree-optimization/104368] " pinskia at gcc dot gnu.org 2022-02-04 7:58 ` rguenth at gcc dot gnu.org 2022-05-06 8:32 ` [Bug tree-optimization/104368] [12/13 " jakub at gcc dot gnu.org 2022-07-26 13:01 ` rguenth at gcc dot gnu.org 2023-05-08 12:23 ` [Bug tree-optimization/104368] [12/13/14 " 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-104368-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).