public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jiu Fu Guo <guojiufu@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/guojiufu/heads/personal-branch)] without number_of_iterations_exit Date: Thu, 20 May 2021 06:28:27 +0000 (GMT) [thread overview] Message-ID: <20210520062827.9ACC63848019@sourceware.org> (raw) https://gcc.gnu.org/g:a18882b0f0764d2adb6878cbfeb1f8b684984850 commit a18882b0f0764d2adb6878cbfeb1f8b684984850 Author: Jiufu Guo <guojiufu@linux.ibm.com> Date: Fri May 14 23:23:45 2021 +0800 without number_of_iterations_exit Diff: --- gcc/tree-ssa-loop-split.c | 7 ------- 1 file changed, 7 deletions(-) diff --git a/gcc/tree-ssa-loop-split.c b/gcc/tree-ssa-loop-split.c index 11d3582dd3d..425593ca70f 100644 --- a/gcc/tree-ssa-loop-split.c +++ b/gcc/tree-ssa-loop-split.c @@ -1666,13 +1666,6 @@ get_ne_cond_branch (struct loop *loop) if (TREE_CODE (iv.base) == INTEGER_CST) continue; - /* If no overflow/wrap happen, no need to split. */ - class tree_niter_desc niter; - if (!number_of_iterations_exit (loop, e, &niter, false, false, NULL)) - continue; - if (niter.control.no_overflow) - return NULL; - /* Check loop is simple to split. */ gcc_assert (bb != loop->latch);
next reply other threads:[~2021-05-20 6:28 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-20 6:28 Jiu Fu Guo [this message] 2021-05-31 5:56 Jiu Fu Guo
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=20210520062827.9ACC63848019@sourceware.org \ --to=guojiufu@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).