On Thursday 03 of September 2009 22:02:06 Christopher Li wrote: > On Thu, Sep 3, 2009 at 11:54 AM, Kamil Dudka<kdudka@xxxxxxxxxx> wrote: > > Two personalities are still not so many ... have you ever looked to the > > gcc code? :-) > > That is why I don't want to start a trend. > > > I didn't say hard, but actually not useful from my point of view. If it's > > easy for you to split my patch to the two pieces, you are welcome to have > > a go at that. We can still wait for opinion of the original authors. > > Perhaps they can bring some light to this problem. > > Fair enough .I need to spend more time to digest this patch. Any progress here? I wouldn't like this to become another downstream patch. I work on a generic layer [1] for processing C sources (for now) supporting SPARSE and gcc 4.5 plug-in as sources. The gcc plug-in [2] now works fairly well and I am going to make the SPARSE client fully equivalent to the plug-in. This will probably need a few more tiny patches for SPARSE to implement what's missing. Is the upstream interested to make SPARSE more useful as a library? Kamil [1]http://dudka.no-ip.org/cgi-bin/gitweb.cgi?p=tools;a=blob_plain;f=sl/code_listener.h [2]http://dudka.no-ip.org/cgi-bin/gitweb.cgi?p=tools;a=blob_plain;f=sl/slplug.c -- 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
