From: David Given <dg@xxxxxxxxxxx>
Currently there is no generic way to derive phy
type information from the instruction flow.
---
linearize.c | 4 +++-
linearize.h | 1 +
2 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/linearize.c b/linearize.c
index fce1ae8..526a710 100644
--- a/linearize.c
+++ b/linearize.c
@@ -55,7 +55,9 @@ static inline int type_size(struct symbol *type)
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 --git a/linearize.h b/linearize.h
index 32b1c1a..0c5e4ef 100644
--- a/linearize.h
+++ b/linearize.h
@@ -71,6 +71,7 @@ struct instruction {
size:24;
struct basic_block *bb;
struct position pos;
+ struct symbol *type;
union {
pseudo_t target;
pseudo_t cond; /* for branch and switch */
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
