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/97064] New: BB vectorization behaves sub-optimal Date: Wed, 16 Sep 2020 06:29:39 +0000 [thread overview] Message-ID: <bug-97064-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97064 Bug ID: 97064 Summary: BB vectorization behaves sub-optimal 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: --- The testcase g++.dg/vect/slp-pr87105.cc ends in _64 = MIN_EXPR <_32, _87>; bBox_6(D)->x0 = _64; _67 = MIN_EXPR <_33, _86>; bBox_6(D)->y0 = _67; _70 = MAX_EXPR <_36, _87>; bBox_6(D)->x1 = _70; _73 = MAX_EXPR <_39, _86>; bBox_6(D)->y1 = _73; thus feeding a 4 element store with a non-uniform SLP opportunity starting with { MIN, MIN, MAX, MAX }. With 2-element vector type vectorization this eventually gets vectorized by splitting the group which is prioritized over just building the { MIN..., MAX } vector from scalars but with 4-element vector type vectorization no splitting is considered and we end up successfully vectorizing just the store with never considering the smaller vector size. So at the moment the testcase PASSes with SSE but fails with AVX.
next reply other threads:[~2020-09-16 6:29 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-16 6:29 rguenth at gcc dot gnu.org [this message] 2020-09-16 6:29 ` [Bug tree-optimization/97064] " rguenth at gcc dot gnu.org 2022-01-11 12:15 ` 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-97064-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).