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/112508] [14 Regression] Size regression when using -Os starting with r14-4089-gd45ddc2c04e Date: Fri, 16 Feb 2024 08:20:08 +0000 [thread overview] Message-ID: <bug-112508-4-QgLPEGLMAi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112508-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112508 --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- We are already doing /* Verify whether the candidate is hot for LOOP. Only do store motion if the candidate's profile count is hot. Statement in cold BB shouldn't be moved out of it's loop_father. */ if (!for_all_locs_in_loop (loop, ref, ref_in_loop_hot_body (loop))) return false; but /* Check the coldest loop between loop L and innermost loop. If there is one cold loop between L and INNER_LOOP, store motion can be performed, otherwise no cold loop means no store motion. get_coldest_out_loop also handles cases when l is inner_loop. */ bool ref_in_loop_hot_body::operator () (mem_ref_loc *loc) { basic_block curr_bb = gimple_bb (loc->stmt); class loop *inner_loop = curr_bb->loop_father; return get_coldest_out_loop (l, inner_loop, curr_bb); } checks that there's a good place to move a store to but it doesn't verify whether there's a store that's likely to be executed in its contained loop. The for_all_locs_in_loop is also happy if _any_ of the stores for the var can be moved to a colder place, likely the intent was to check that for all of the stores (though it's unlikely to differ in simple cases). This all doesn't distinguish between always and not always executed refs.
next prev parent reply other threads:[~2024-02-16 8:20 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-13 11:11 [Bug tree-optimization/112508] New: " theodort at inf dot ethz.ch 2023-11-13 11:15 ` [Bug tree-optimization/112508] " rguenth at gcc dot gnu.org 2024-02-15 23:08 ` roger at nextmovesoftware dot com 2024-02-16 8:11 ` rguenth at gcc dot gnu.org 2024-02-16 8:20 ` rguenth at gcc dot gnu.org [this message] 2024-03-07 21:02 ` law at gcc dot gnu.org 2024-05-07 7:42 ` [Bug tree-optimization/112508] [14/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-112508-4-QgLPEGLMAi@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).