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)] change base<bnd to base<=bnd Date: Tue, 22 Jun 2021 02:36:47 +0000 (GMT) [thread overview] Message-ID: <20210622023647.9DFDF384605A@sourceware.org> (raw) https://gcc.gnu.org/g:2801d6286a7b55139d4ff026ca552f47eba20348 commit 2801d6286a7b55139d4ff026ca552f47eba20348 Author: Jiufu Guo <guojiufu@linux.ibm.com> Date: Mon Jun 21 13:14:39 2021 +0800 change base<bnd to base<=bnd Diff: --- gcc/tree-ssa-loop-split.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/gcc/tree-ssa-loop-split.c b/gcc/tree-ssa-loop-split.c index bf9cee66e92..c9d161565e4 100644 --- a/gcc/tree-ssa-loop-split.c +++ b/gcc/tree-ssa-loop-split.c @@ -1774,9 +1774,8 @@ get_wrap_assumption (class loop *loop, edge *exit, idx_elements &data) tree bnd_type = TREE_TYPE (bnd); if (!INTEGRAL_TYPE_P (bnd_type) || !TYPE_UNSIGNED (bnd_type)) continue; - if (TREE_CODE (bnd) == INTEGER_CST - && (tree_int_cst_equal (bnd, TYPE_MAX_VALUE (bnd_type)) - || tree_int_cst_equal (bnd, TYPE_MIN_VALUE (bnd_type)))) + if (tree_int_cst_equal (bnd, TYPE_MAX_VALUE (bnd_type)) + || tree_int_cst_equal (bnd, TYPE_MIN_VALUE (bnd_type))) continue; /* Check if it is "idx != bnd" or "idx < bnd". */ @@ -1823,7 +1822,7 @@ get_wrap_assumption (class loop *loop, edge *exit, idx_elements &data) = fold_build2 (expect_code1, boolean_type_node, bnd, max_min_bnd); no_wrap = fold_build2 (TRUTH_AND_EXPR, boolean_type_node, no_wrap, - fold_build2 (expect_code, boolean_type_node, base, bnd)); + fold_build2 (expect_code1, boolean_type_node, base, bnd)); if (integer_zerop (no_wrap)) continue;
reply other threads:[~2021-06-22 2:36 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=20210622023647.9DFDF384605A@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).