From: Daniel Wagner <daniel.wagner@bmw-carit.de>
To: linux-sparse@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Christopher Li <sparse@chrisli.org>,
Daniel Wagner <daniel.wagner@bmw-carit.de>
Subject: [FAIL 3/5] linearize: Add context symbol name when showing context instructions
Date: Wed, 17 Feb 2016 10:51:33 +0100 [thread overview]
Message-ID: <1455702695-6199-4-git-send-email-daniel.wagner@bmw-carit.de> (raw)
In-Reply-To: <1455702695-6199-1-git-send-email-daniel.wagner@bmw-carit.de>
Signed-off-by: Daniel Wagner <daniel.wagner@bmw-carit.de>
---
linearize.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/linearize.c b/linearize.c
index c6ada1e..da3a190 100644
--- a/linearize.c
+++ b/linearize.c
@@ -441,7 +441,7 @@ const char *show_instruction(struct instruction *insn)
break;
case OP_CONTEXT:
- buf += sprintf(buf, "%s%d", insn->check ? "check: " : "", insn->increment);
+ buf += sprintf(buf, "%s %s%d", insn->context_expr? show_ident(insn->context_expr->symbol_name) : "", insn->check ? "check: " : "", insn->increment);
break;
case OP_RANGE:
buf += sprintf(buf, "%s between %s..%s", show_pseudo(insn->src1), show_pseudo(insn->src2), show_pseudo(insn->src3));
--
2.5.0
next prev parent reply other threads:[~2016-02-17 9:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 9:51 [FAIL 0/5] Static lock analysis Daniel Wagner
2016-02-17 9:51 ` [FAIL 1/5] parse: Add comment to struct statement Daniel Wagner
2016-02-17 9:51 ` [FAIL 2/5] inspect: Show context information Daniel Wagner
2016-02-17 9:51 ` Daniel Wagner [this message]
2016-02-17 9:51 ` [FAIL 4/5] parse: Add acquire, release, requires and guarded_by attributes Daniel Wagner
2016-02-17 9:51 ` [FAIL 5/5] test-locks: Add lock tester Daniel Wagner
2016-02-17 23:05 ` [FAIL 0/5] Static lock analysis Christopher Li
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=1455702695-6199-4-git-send-email-daniel.wagner@bmw-carit.de \
--to=daniel.wagner@bmw-carit.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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).