public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/marxin/heads/loop-unswitch-improvement)] Add one more comment. Date: Mon, 22 Nov 2021 12:52:51 +0000 (GMT) [thread overview] Message-ID: <20211122125251.AB94E3858426@sourceware.org> (raw) https://gcc.gnu.org/g:897eedc407c738f661b505e7ad600a3a2b269454 commit 897eedc407c738f661b505e7ad600a3a2b269454 Author: Martin Liska <mliska@suse.cz> Date: Mon Nov 22 13:52:32 2021 +0100 Add one more comment. Diff: --- gcc/tree-ssa-loop-unswitch.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/gcc/tree-ssa-loop-unswitch.c b/gcc/tree-ssa-loop-unswitch.c index ae2b5e1239a..6895e5b8bb9 100644 --- a/gcc/tree-ssa-loop-unswitch.c +++ b/gcc/tree-ssa-loop-unswitch.c @@ -208,7 +208,8 @@ is_maybe_undefined (const tree name, gimple *stmt, class loop *loop) /* Checks whether we can unswitch LOOP on condition at end of BB -- one of its basic blocks (for what it means see comments below). - RANGER is gimple ranger used in this pass. */ + RANGER is gimple ranger used in this pass and unswitch_predicate is returned + if there is an opportunity for unswitching. */ static unswitch_predicate * tree_may_unswitch_on (basic_block bb, class loop *loop, gimple_ranger *ranger)
reply other threads:[~2021-11-22 12:52 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20211122125251.AB94E3858426@sourceware.org \ --to=marxin@gcc.gnu.org \ --cc=gcc-cvs@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).