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 v2 0/2] split OP_BR between OP_BR & OP_CBR
Date: Tue, 28 Feb 2017 14:30:26 +0100 [thread overview]
Message-ID: <20170228133028.45237-1-luc.vanoostenryck@gmail.com> (raw)
In-Reply-To: <CANeU7Q=60E+2tvn=bdjaYnZFS3U3PMiTTq0=eYS-NkPDK3aJNA@mail.gmail.com>
This series introduces a new instruction opcode (OP_CBR)
for conditional branches. Previously both conditional and
non-conditional branches used the OP_BR opcode which is
now reserved for non-conditional branches.
The motivation is the correctness of the test between
the two kind of branches and an added benefit is the
simplicity of this test now.
Changes since v1:
- add missing '/* fall through */'
- convert 2 more tests of ->cond/->bb_{true,false}
into tests of ->opcode == OP_CBR/OP_BR
Luc Van Oostenryck (2):
split OP_BR between unconditional & conditional: OP_CBR
remove unused helper is_branch_goto()
example.c | 2 +
flow.c | 17 +++--
linearize.c | 14 +++--
linearize.h | 5 +-
liveness.c | 3 +-
simplify.c | 15 ++---
sparse-llvm.c | 25 ++++----
validation/loop-linearization.c | 136 ++++++++++++++++++++++++++++++++++++++++
8 files changed, 179 insertions(+), 38 deletions(-)
create mode 100644 validation/loop-linearization.c
--
2.11.1
next prev parent reply other threads:[~2017-02-28 13:33 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 ` Luc Van Oostenryck [this message]
2017-02-28 13:30 ` [PATCH v2 " 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 ` [PATCH " Luc Van Oostenryck
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=20170228133028.45237-1-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 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 NNTP newsgroup(s).