All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Christopher Li <sparse@chrisli.org>,
	Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 2/2] remove unused helper is_branch_goto()
Date: Sat, 18 Feb 2017 02:28:48 +0100	[thread overview]
Message-ID: <20170218012848.27417-3-luc.vanoostenryck@gmail.com> (raw)
In-Reply-To: <20170218012848.27417-1-luc.vanoostenryck@gmail.com>

This helper is also made unneeded since the introduction of OP_CBR.

Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
---
 linearize.h | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/linearize.h b/linearize.h
index 2aa255154..bac82d7ff 100644
--- a/linearize.h
+++ b/linearize.h
@@ -237,10 +237,6 @@ struct basic_block {
 	};
 };
 
-static inline int is_branch_goto(struct instruction *br)
-{
-	return br && br->opcode==OP_BR && (!br->bb_true || !br->bb_false);
-}
 
 static inline void add_bb(struct basic_block_list **list, struct basic_block *bb)
 {
-- 
2.11.0


      parent reply	other threads:[~2017-02-18  1:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-18  1:28 [PATCH 0/2] split OP_BR between OP_BR & OP_CBR Luc Van Oostenryck
2017-02-18  1:28 ` [PATCH 1/2] split OP_BR between unconditional & conditional: OP_CBR Luc Van Oostenryck
2017-02-27 15:02   ` Christopher Li
2017-02-27 21:22     ` Luc Van Oostenryck
2017-02-28 13:30     ` [PATCH v2 0/2] split OP_BR between OP_BR & OP_CBR Luc Van Oostenryck
2017-02-28 13:30       ` [PATCH v2 1/2] split OP_BR between unconditional & conditional: OP_CBR Luc Van Oostenryck
2017-02-28 13:30       ` [PATCH v2 2/2] remove unused helper is_branch_goto() Luc Van Oostenryck
2017-02-18  1:28 ` Luc Van Oostenryck [this message]

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=20170218012848.27417-3-luc.vanoostenryck@gmail.com \
    --to=luc.vanoostenryck@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=sparse@chrisli.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.