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] fix rem_usage()
Date: Sun, 27 Dec 2020 10:27:57 +0100 [thread overview]
Message-ID: <20201227092759.30999-1-luc.vanoostenryck@gmail.com> (raw)
These two patches fix a bug with rem_usage(), after having removed the
last element of a def-use list, tries to kill the defining instruction
although only PSEUDO_REGs and PSEUDO_PHIs have one.
Luc Van Oostenryck (2):
add helper has_definition()
fix rem_usage()
linearize.h | 5 +++++
simplify.c | 2 +-
2 files changed, 6 insertions(+), 1 deletion(-)
--
2.29.2
next reply other threads:[~2020-12-27 9:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-27 9:27 Luc Van Oostenryck [this message]
2020-12-27 9:27 ` [PATCH 1/2] add helper has_definition() Luc Van Oostenryck
2020-12-28 17:20 ` Ramsay Jones
2020-12-27 9:27 ` [PATCH 2/2] fix rem_usage() Luc Van Oostenryck
2020-12-28 17:22 ` Ramsay Jones
2020-12-28 21:39 ` Luc Van Oostenryck
2020-12-28 22:09 ` Ramsay Jones
2020-12-28 22:30 ` Ramsay Jones
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=20201227092759.30999-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).