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)] code format
Date: Wed,  2 Jun 2021 07:58:01 +0000 (GMT)	[thread overview]
Message-ID: <20210602075801.6A8433948A8D@sourceware.org> (raw)

https://gcc.gnu.org/g:2d545de6899852653f7657c66300f1a338ebb8df

commit 2d545de6899852653f7657c66300f1a338ebb8df
Author: Jiufu Guo <guojiufu@linux.ibm.com>
Date:   Wed Jun 2 15:47:59 2021 +0800

    code format

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 791508e4f03..fa79c257167 100644
--- a/gcc/tree-ssa-loop-split.c
+++ b/gcc/tree-ssa-loop-split.c
@@ -1681,8 +1681,7 @@ get_ne_cond_branch (struct loop *loop)
 	  if (idx != prev && idx != next)
 	    continue;
 
-	  gimple_stmt_iterator gsi
-	    = gsi_start_nondebug_after_labels_bb (bb);
+	  gimple_stmt_iterator gsi = gsi_start_nondebug_after_labels_bb (bb);
 	  if (gsi_end_p (gsi))
 	    continue;
 	  gimple *s1 = gsi_stmt (gsi);
@@ -1732,8 +1731,8 @@ split_ne_loop (struct loop *loop, edge cond_e)
   /* Link the exit cond edge to new loop.  */
   gcond *break_cond = as_a<gcond *> (gimple_copy (gc));
   edge pred_e = single_pred_edge (loop->latch);
-  bool simple_loop = pred_e && pred_e->src == cond_e->src
-		     && empty_block_p (loop->latch);
+  bool simple_loop
+    = pred_e && pred_e->src == cond_e->src && empty_block_p (loop->latch);
   if (simple_loop)
     gimple_cond_set_code (break_cond, down_code);
   else


                 reply	other threads:[~2021-06-02  7:58 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=20210602075801.6A8433948A8D@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: link
Be 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).