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/23970] loop-invariant-motion is not doing it's work Date: Fri, 01 Sep 2023 09:17:52 +0000 [thread overview] Message-ID: <bug-23970-4-JO4VKVErhq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-23970-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=23970 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- Unswitching does this as a separate transform now, the "hoist guards" transform. It's even done completely separate now: unsigned int tree_ssa_unswitch_loops (function *fun) { bool changed_unswitch = false; bool changed_hoist = false; auto_edge_flag ignored_edge_flag (fun); ranger = enable_ranger (fun); /* Go through all loops starting from innermost, hoisting guards. */ for (auto loop : loops_list (fun, LI_FROM_INNERMOST)) { if (loop->inner) changed_hoist |= tree_unswitch_outer_loop (loop); } /* Go through innermost loops, unswitching on invariant predicates within those. */ ... the question is how we'd call the "cheap" unswitching transform. I guess simply testing optimize > 2 || opt_enabled or so isn't quite desirable. Note it's possible to separate this into an entirely separate pass as well.
next prev parent reply other threads:[~2023-09-01 9:17 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-23970-4@http.gcc.gnu.org/bugzilla/> 2021-12-26 22:07 ` pinskia at gcc dot gnu.org 2023-09-01 9:17 ` rguenth at gcc dot gnu.org [this message] 2005-09-19 18:52 [Bug tree-optimization/23970] New: " rguenth at gcc dot gnu dot org 2005-09-19 18:52 ` [Bug tree-optimization/23970] " rguenth at gcc dot gnu dot org 2005-09-20 13:34 ` rakdver at gcc dot gnu dot 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-23970-4-JO4VKVErhq@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).