On Tue, Mar 7, 2017 at 6:39 AM, Dibyendu Majumdar <mobile@xxxxxxxxxxxxxxx> wrote: > 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 Adding an additional argument is a very big change. > changes are related to initialization of the various global structures > used by Sparse. In your usage case, is it possible to use some kind of lock to avoid racing to initialize 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. May be need a script of some short to automate part of the change. Do you have that big and painful change already? 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
