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/5] use replace_with_pseudo() for simplify_memops()
Date: Sun, 29 Nov 2020 15:49:17 +0100 [thread overview]
Message-ID: <20201129144922.56209-1-luc.vanoostenryck@gmail.com> (raw)
This series contains a few patches related to replace_with_pseudo()
in preparation for some more consequential changes in memops
simplification.
Luc Van Oostenryck (5):
let replace_with_pseudo() use kill_instruction()
make a header for simplification
make replace_with_pseudo() extern
memops: move rewrite_load_instruction() here
replace convert_load_instruction() by replace_with_pseudo()
flow.c | 48 +-----------------------------------------------
flow.h | 3 ---
memops.c | 46 ++++++++++++++++++++++++++++++++++++++++++++--
optimize.c | 1 +
simplify.c | 21 +++------------------
simplify.h | 10 ++++++++++
ssa.c | 9 +++++----
7 files changed, 64 insertions(+), 74 deletions(-)
create mode 100644 simplify.h
--
2.29.2
next reply other threads:[~2020-11-29 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 14:49 Luc Van Oostenryck [this message]
2020-11-29 14:49 ` [PATCH 1/5] let replace_with_pseudo() use kill_instruction() Luc Van Oostenryck
2020-11-29 14:49 ` [PATCH 2/5] make a header for simplification Luc Van Oostenryck
2020-11-29 14:49 ` [PATCH 3/5] make replace_with_pseudo() extern Luc Van Oostenryck
2020-11-29 14:49 ` [PATCH 4/5] memops: move rewrite_load_instruction() here Luc Van Oostenryck
2020-11-29 14:49 ` [PATCH 5/5] replace convert_load_instruction() by replace_with_pseudo() 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=20201129144922.56209-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).