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/4] fix SSA conversion of mismatched memops
Date: Wed, 10 Mar 2021 00:42:28 +0100 [thread overview]
Message-ID: <20210309234232.50889-1-luc.vanoostenryck@gmail.com> (raw)
The SSA conversion works under the assumption that all the memory
operations on a given symbol always refer to the same object
(same size, offset and type/kind of object) but doesn't check this
well enough. This series now does.
Luc Van Oostenryck (4):
ssa: add some testcases for mismatched memops
ssa: the sparse set is not needed
ssa: avoid SSA conversion of packed bitfields
ssa: fix conversion with mismatched size or offset
Makefile | 1 -
linearize.h | 2 +-
ssa.c | 111 +++++++++++++++++++++------
sset.c | 28 -------
sset.h | 56 --------------
validation/mem2reg/not-same-memop0.c | 48 ++++++++++++
validation/mem2reg/packed-bitfield.c | 35 +++++++++
7 files changed, 170 insertions(+), 111 deletions(-)
delete mode 100644 sset.c
delete mode 100644 sset.h
create mode 100644 validation/mem2reg/not-same-memop0.c
create mode 100644 validation/mem2reg/packed-bitfield.c
--
2.30.0
next reply other threads:[~2021-03-09 23:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 23:42 Luc Van Oostenryck [this message]
2021-03-09 23:42 ` [PATCH 1/4] ssa: add some testcases for mismatched memops Luc Van Oostenryck
2021-03-09 23:42 ` [PATCH 2/4] ssa: the sparse set is not needed Luc Van Oostenryck
2021-03-09 23:42 ` [PATCH 3/4] ssa: avoid SSA conversion of packed bitfields Luc Van Oostenryck
2021-03-09 23:42 ` [PATCH 4/4] ssa: fix conversion with mismatched size or offset 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=20210309234232.50889-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).