On Wed, Feb 1, 2012 at 5:50 PM, Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx> wrote: > But in both cases the type itself is a struct symbol isn't it ? Either a > function def as Linus patch provides or base_type which is a struct > symbol too.... Yes, sparse type itself is "struct symbol" pointer. I see. You mean construct a LLVM value from a give sparse type. Sure, that is value point. I actually did that once before, in my llvm hack attempt. I lost that code base due to a hard drive failure. > Sure if we have a consistent pseudo->type that covers both cases then we > can just pass that along, I don't mind. Yes, that is the point my counter RFC. When you look at it, the insn->fntype is really type of the insn->func pseudo. That is a one off thing for call instruction. Store type inside pseudo provide the same functionality and unify how to get type from pseudo. Chris -- 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
