From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 0/2] cleanup REPEAT_SYMBOL_CLEANUP & kill_insn()
Date: Sat, 21 Nov 2020 23:46:55 +0100 [thread overview]
Message-ID: <20201121224657.96038-1-luc.vanoostenryck@gmail.com> (raw)
This series contains 2 patches doing some cleanups related
to REPEAT_SYMBOL_CLEANUP and instruction killing.
Note: these pacthes must be applied on top of the previous
641cf2c29528 ("fix kill_insn(OP_SETVAL)").
Luc Van Oostenryck (2):
remove unneeded REPEAT_SYMBOL_CLEANUP
simplify kill_insn() of unops and unop-ish instructions
flow.c | 3 +--
flow.h | 1 -
simplify.c | 25 +++++++------------------
3 files changed, 8 insertions(+), 21 deletions(-)
base-commit: 641cf2c295285ee15f35dbcfd85367ca61259be0
--
2.29.2
next reply other threads:[~2020-11-21 22:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 22:46 Luc Van Oostenryck [this message]
2020-11-21 22:46 ` [PATCH 1/2] remove unneeded REPEAT_SYMBOL_CLEANUP Luc Van Oostenryck
2020-11-21 22:46 ` [PATCH 2/2] simplify kill_insn() of unops and unop-ish instructions 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=20201121224657.96038-1-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.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).