On 6 March 2017 at 19:26, Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx> wrote: > On Mon, Mar 6, 2017 at 7:47 PM, Dibyendu Majumdar >> Because I have a modified >> version of Sparse with all global state removed, merging changes is a >> bit painful as it has be done manually. > > I can imagine this. > I, of course, hve no idea why you (have to) do this but I can only very strongly > advice you to try to avoid this as much as possible. > As I mentioned before I am using Sparse to create a JIT compiler for C. So this needs to be callable as a library - and I need the ability to call it many times. Moreover it must be possible to call several instances of Sparse simultaneously without conflict. To achieve all this, all global state is held in a set of structures. The main change is that the most function calls have an additional argument. The other changes are related to initialization of the various global structures used by Sparse. Generally I try to keep the code as far as possible identical to Sparse except for these changes. Even so merging is very painful. Regards Dibyendu -- 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
