From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Eisele Subject: Re: Fwd: dependency tee from c parser entities downto token Date: Tue, 08 May 2012 08:38:53 +0200 Message-ID: <4FA8BF7D.60606@gaisler.com> References: <4F967865.60809@gaisler.com> <4FA38635.5060300@gaisler.com> <4FA3B14A.3070609@gaisler.com> <4FA44E3D.6020504@gmail.com> <4FA4EAD6.1040206@gmail.com> <4FA5B9E8.7010208@ gmail.com> <4FA767BD.8060703@gaisler.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mail176c2.megamailservers.com ([69.49.111.76]:56612 "EHLO mail176c2.megamailservers.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753142Ab2EHGtB (ORCPT ); Tue, 8 May 2012 02:49:01 -0400 In-Reply-To: Sender: linux-sparse-owner@vger.kernel.org List-Id: linux-sparse@vger.kernel.org To: Christopher Li Cc: Konrad Eisele , Linux-Sparse Christopher Li wrote: > Hi Konrad, > > I appreciate all the input. How about this, I am going to implement > the core sparse > part of the API change. You will be the first customer that use that > API. I think this > API is also useful for people want to do source code transformations > using sparse. > They usually want to manipulate the source code stream before the > pre-processing. > > Anyway, I am hacking a branch starting from the last patch I send out. > I am adding the test program to demonstrate how to use those hooks to accomplish > different things. You just need to keep telling me what extra feature > you want from > the API. I can try to incorporate them with the demo program. Yea, I think it is better that way. You should implement it yourself first, it kind of takes too long otherwise :-). Still I'm kind of curious how you can trace macro expansion with just 1 callback but I'll like to be surprised. -- Konrad > > I will let you know when I have the branch ready. > > Chris > -- > To unsubscribe from this list: send the line "unsubscribe linux-sparse" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > >