From: Christopher Li <sparse@chrisli.org>
To: linux-sparse@vger.kernel.org
Cc: Josh Triplett <josh@freedesktop.org>
Subject: [PATCH 5] Update usage chain for dead instruction.
Date: Tue, 16 Jan 2007 18:38:04 -0800 [thread overview]
Message-ID: <20070117023804.GE962@chrisli.org> (raw)
Branch like that:
br %c, 0x10, 0x10
Will be simplify and removed. But the usage information is not updated.
Signed-Off-By: Christopher Li<sparse@chrisli.org>
Index: sparse/flow.c
===================================================================
--- sparse.orig/flow.c 2006-12-21 20:48:07.000000000 -0800
+++ sparse/flow.c 2006-12-21 22:20:44.000000000 -0800
@@ -987,7 +987,7 @@ out:
replace_bb_in_list(&child->parents, bb, parent, 0);
} END_FOR_EACH_PTR(child);
- delete_last_instruction(&parent->insns);
+ kill_instruction(delete_last_instruction(&parent->insns));
FOR_EACH_PTR(bb->insns, insn) {
if (insn->bb) {
assert(insn->bb == bb);
next reply other threads:[~2007-01-17 3:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 2:38 Christopher Li [this message]
2007-01-17 5:20 ` [PATCH 5] Update usage chain for dead instruction Josh Triplett
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=20070117023804.GE962@chrisli.org \
--to=sparse@chrisli.org \
--cc=josh@freedesktop.org \
--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).