From: David Given <dg@cowlark.com>
To: linux-sparse@vger.kernel.org
Subject: Adding type information to instructions
Date: Sat, 05 Jul 2008 00:43:24 +0100 [thread overview]
Message-ID: <486EB59C.100@cowlark.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1231 bytes --]
I've been having trouble finding the types of pseudos; the approach I've
been using, which is to follow the chain of pseudo's definers until I
find an instruction with enough type information to use, turns out to
fail utterly on OP_LOAD instructions; I can't find any way of getting
enough information from the opcode's arguments to determine the type of
the target.
As a result, I've had to make a minor patch to the lineariser code.
Given that the lineariser knows the information I need at the point
where it generates the instruction, it would seem to make sense to tag
the instruction with the type. This is made quite easy by the way that
the lineariser has a allocate-typed-instruction function.
Patch enclosed; it's very simple.
Does this seem like a reasonable approach? Is it something that would be
useful to have in the base builds? Are there any ramifications I should
be aware of?
--
┌─── dg@cowlark.com ───── http://www.cowlark.com ─────
│ "I have always wished for my computer to be as easy to use as my
│ telephone; my wish has come true because I can no longer figure out
│ how to use my telephone." --- Bjarne Stroustrup
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: type.patch --]
[-- Type: text/x-diff; name="type.patch", Size: 882 bytes --]
diff -rwu sparse.orig/linearize.c sparse/linearize.c
--- sparse.orig/linearize.c 2008-06-28 22:44:21.714555764 +0100
+++ sparse/linearize.c 2008-06-30 23:20:30.777932755 +0100
@@ -55,7 +55,9 @@
static struct instruction *alloc_typed_instruction(int opcode, struct symbol *type)
{
- return alloc_instruction(opcode, type_size(type));
+ struct instruction *insn = alloc_instruction(opcode, type_size(type));
+ insn->type = type;
+ return insn;
}
static struct entrypoint *alloc_entrypoint(void)
diff -rwu sparse.orig/linearize.h sparse/linearize.h
--- sparse.orig/linearize.h 2008-06-28 22:44:21.714555764 +0100
+++ sparse/linearize.h 2008-06-30 23:20:04.425933822 +0100
@@ -71,6 +71,7 @@
size:24;
struct basic_block *bb;
struct position pos;
+ struct symbol *type;
union {
pseudo_t target;
pseudo_t cond; /* for branch and switch */
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next reply other threads:[~2008-07-04 23:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 23:43 David Given [this message]
2008-07-07 17:42 ` Adding type information to instructions Josh Triplett
2008-07-07 20:08 ` Chris 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=486EB59C.100@cowlark.com \
--to=dg@cowlark.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).