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/110935] New: Missed BB reduction vectorization because of missed eliding of a permute Date: Mon, 07 Aug 2023 13:28:26 +0000 [thread overview] Message-ID: <bug-110935-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110935 Bug ID: 110935 Summary: Missed BB reduction vectorization because of missed eliding of a permute Product: gcc Version: 13.1.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: --- double vals[16]; double test () { vals[0]++; return vals[2] + vals[4] + vals[1] + vals[3]; } has the reduction not vectorized with -ffast-math because t.c:5:38: note: === vect_slp_analyze_operations === t.c:5:38: note: ==> examining statement: _8 = vals[3]; t.c:5:38: missed: BB vectorization with gaps at the end of a load is not supported t.c:5:44: missed: not vectorized: relevant stmt not supported: _8 = vals[3]; t.c:5:38: note: removing SLP instance operations starting from: _11 = _7 + _8; t.c:5:38: missed: not vectorized: bad operation in basic block. we fail to elide the load permutation (BB vect allows a consecutive sub-set): t.c:5:38: note: Final SLP tree for instance 0x51c8d60: t.c:5:38: note: node 0x5285860 (max_nunits=2, refcnt=2) vector(2) double t.c:5:38: note: op template: _8 = vals[3]; t.c:5:38: note: stmt 0 _8 = vals[3]; t.c:5:38: note: stmt 1 _6 = vals[1]; t.c:5:38: note: stmt 2 _3 = vals[2]; t.c:5:38: note: stmt 3 _4 = vals[4]; t.c:5:38: note: load permutation { 3 1 2 4 } t.c:5:38: note: === vect_match_slp_patterns === t.c:5:38: note: Analyzing SLP tree 0x5285860 for patterns t.c:5:38: note: SLP optimize permutations: t.c:5:38: note: 1: { 2, 0, 1, 3 } t.c:5:38: note: SLP optimize partitions: t.c:5:38: note: ------------- t.c:5:38: note: partition 0 (layout 0): t.c:5:38: note: nodes: t.c:5:38: note: - 0x5285860: t.c:5:38: note: weight: 1.000000 t.c:5:38: note: op template: _8 = vals[3]; t.c:5:38: note: edges: t.c:5:38: note: layout 0: (*) t.c:5:38: note: {depth: 0.000000, total: 0.000000} t.c:5:38: note: + {depth: 1.000000, total: 1.000000} t.c:5:38: note: + {depth: 0.000000, total: 0.000000} t.c:5:38: note: = {depth: 1.000000, total: 1.000000} t.c:5:38: note: layout 1: t.c:5:38: note: {depth: 0.000000, total: 0.000000} t.c:5:38: note: + {depth: 1.000000, total: 1.000000} t.c:5:38: note: + {depth: 0.000000, total: 0.000000} t.c:5:38: note: = {depth: 1.000000, total: 1.000000} t.c:5:38: note: recording new base alignment for &vals alignment: 32 misalignment: 0 based on: _1 = vals[0]; t.c:5:38: note: === vect_slp_analyze_instance_alignment ===
next reply other threads:[~2023-08-07 13:28 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-07 13:28 rguenth at gcc dot gnu.org [this message] 2023-08-07 13:30 ` [Bug tree-optimization/110935] " rguenth at gcc dot gnu.org 2023-09-05 9:01 ` rsandifo at gcc dot gnu.org 2023-09-12 7:43 ` rguenther at suse dot de 2024-01-21 2:00 ` pinskia at gcc dot gnu.org 2024-04-15 13:33 ` 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-110935-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).