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/113080] Missed optimization of loop invariant elimination Date: Tue, 19 Dec 2023 09:50:22 +0000 [thread overview] Message-ID: <bug-113080-4-QSzbl8Krjq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113080-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113080 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2023-12-19 Ever confirmed|0 |1 Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Status|UNCONFIRMED |ASSIGNED --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed. We're considering the final value replacement of the 't' reduction expensive. It's ((b_lsm.10_8 + a_lsm.9_9) + t_10(D)) + (b_lsm.10_8 + a_lsm.9_9) * 99 and since there's a shared tree (b_lsm.10_8 + a_lsm.9_9) which we'd duplicate (materializing as GIMPLE fails to immediately CSE). bool expression_expensive_p (tree expr, bool *cond_overflow_p) { hash_map<tree, uint64_t> cache; uint64_t expanded_size = 0; *cond_overflow_p = false; return (expression_expensive_p (expr, cond_overflow_p, cache, expanded_size) || expanded_size > cache.elements ()); } where expanded_size is 5 but cache.elements () is 4 (we grow because of unsharing). Allowing a little bit of unsharing fixes this. Even better would be of course an unsharing mechanism that would "save" the shared parts to a gimple sequence (we need to unshare because gimplification is destructive and the SCEV result contains trees that can be part of the SCEV cache which we may not alter).
next prev parent reply other threads:[~2023-12-19 9:50 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-19 7:45 [Bug tree-optimization/113080] New: " 652023330028 at smail dot nju.edu.cn 2023-12-19 9:50 ` rguenth at gcc dot gnu.org [this message] 2023-12-19 12:32 ` [Bug tree-optimization/113080] " cvs-commit at gcc dot gnu.org 2023-12-19 12: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-113080-4-QSzbl8Krjq@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).