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/95845] Failure to optimize vector load made in separate operations to single load Date: Wed, 24 Jun 2020 06:51:57 +0000 [thread overview] Message-ID: <bug-95845-4-7NJboj23Cp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95845-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95845 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rguenth at gcc dot gnu.org Last reconfirmed| |2020-06-24 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- So this is VIEW_CONVERT_EXPR<float[2]>(r)[0] = *ptr; VIEW_CONVERT_EXPR<float[2]>(r)[1] = *(ptr + 4); from the FEs and _1 = *ptr_4(D); r_6 = BIT_INSERT_EXPR <r_5(D), _1, 0>; _2 = MEM[(const float *)ptr_4(D) + 4B]; r_7 = BIT_INSERT_EXPR <r_6, _2, 32>; after SSA rewrite. There's no further combining of inserts happening, I guess forwprop might want to see whether an insert chain forms a full CTOR. BB vectorization might also a candidate to look at but it would be quite late. The issue with forwprop is to somehow avoid quadraticness in searching the chain which will be difficult given it's structure. One possibility would be to perform a forward search from BIT_INSERT_EXPRs with a default def arg and mark the last BIT_INSERT_EXPR in a single-use chain as to be processed. Or declare it not a problem.
next prev parent reply other threads:[~2020-06-24 6:51 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-23 15:43 [Bug tree-optimization/95845] New: " gabravier at gmail dot com 2020-06-24 6:51 ` rguenth at gcc dot gnu.org [this message] 2021-09-01 23:29 ` [Bug tree-optimization/95845] " gabravier at gmail dot com 2021-09-02 7:01 ` rguenth at gcc dot gnu.org 2023-05-12 6:23 ` 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-95845-4-7NJboj23Cp@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).