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/guojiufu-branch)] update comments and do not update case pr98064.cc Date: Wed, 9 Jun 2021 11:20:06 +0000 (GMT) [thread overview] Message-ID: <20210609112006.9ED563972017@sourceware.org> (raw) https://gcc.gnu.org/g:ce08a33145e1b5736595c4c5a600ea5443103d03 commit ce08a33145e1b5736595c4c5a600ea5443103d03 Author: Jiufu Guo <guojiufu@linux.ibm.com> Date: Wed Jun 9 19:17:02 2021 +0800 update comments and do not update case pr98064.cc Diff: --- gcc/testsuite/g++.dg/vect/pr98064.cc | 4 +--- gcc/tree-ssa-loop-split.c | 10 +++++----- 2 files changed, 6 insertions(+), 8 deletions(-) diff --git a/gcc/testsuite/g++.dg/vect/pr98064.cc b/gcc/testsuite/g++.dg/vect/pr98064.cc index dcb2985d05a..74043ce7725 100644 --- a/gcc/testsuite/g++.dg/vect/pr98064.cc +++ b/gcc/testsuite/g++.dg/vect/pr98064.cc @@ -1,7 +1,5 @@ // { dg-do compile } -// { dg-additional-options "-O3 -Wno-stringop-overflow" } -/* There is warning message when "short g = var_8; g; g++" - is optimized/analyzed as string operation,e.g. memset. */ +// { dg-additional-options "-O3" } const long long &min(const long long &__a, long long &__b) { if (__b < __a) diff --git a/gcc/tree-ssa-loop-split.c b/gcc/tree-ssa-loop-split.c index 0365b6d069e..e9f23b32186 100644 --- a/gcc/tree-ssa-loop-split.c +++ b/gcc/tree-ssa-loop-split.c @@ -1664,9 +1664,9 @@ get_ne_cond_branch (struct loop *loop, tree *step) return e; /* If exit edge is at end of header, and header contains i++ or ++i, - only, it is simple to link the split loops: jump from the end of - one loop header to the new loop header, and use unchanged PHI - result of first loop as the entry PHI value of the second loop. */ + only, it is simple to link the split loops: jump from the end of + one loop header to the new loop header, and use unchanged PHI result + of the first loop as the entry PHI value of the second loop. */ if (bb == loop->header) { /* Only one phi. */ @@ -1793,7 +1793,7 @@ L_H: i++; goto L_H; -The "i!=N" is like "i>N || i<N", then it could be transform to: +The "i!=N" is like "i>N || i<N", then it could be transformed to: L_H: if (i>N) @@ -1810,7 +1810,7 @@ L1_H: i++; goto L1_H; -The loop with "i<N" is in favor both GIMPLE and RTL passes. */ +The loop with "i<N" is in favor of both GIMPLE and RTL passes. */ static bool split_loop_on_ne_cond (class loop *loop)
reply other threads:[~2021-06-09 11:20 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=20210609112006.9ED563972017@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).