On Fri, Feb 3, 2012 at 1:09 AM, Pekka Enberg <penberg@xxxxxxxxxx> wrote: > On Thu, Feb 2, 2012 at 4:10 AM, Christopher Li <sparse@xxxxxxxxxxx> wrote: >> 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. > > Ping? I'd really like to have this bug fixed because it affects basic > "hello, world" on x86-64 and PPC. Hi Pekka, Sorry I get really spaced. Can you continue apply that into your sparse-llvm repository? The insn->type to pseudo->ctype change is actually impact a lot of code. I haven't able to complete it yet. On the other hand, I don't want you to block on it. The more I look at it, the more I believe this is the right thing to do. Pseudo come from expressions, the pseudo->ctype is just the expr->ctype. We will merge the sparse-llvm again when I get this sort out. One good thing about git is that branch and merge is really easy. I you to continue the sparse-llvm repository. I can submit some llvm related patch for you to review as well. sparse-llvm.c is the biggest user of insn->type right now. I want to simplify the usage a little bit. Thanks 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
