On Sun, Mar 12, 2017 at 9:13 PM, Dibyendu Majumdar <mobile@xxxxxxxxxxxxxxx> wrote: > Hi > > As a measure of the progress made in the past few days (thanks Luc!) - > I have a bunch of test cases that now pass. More tests will be added. > > Note that there are fixes in my project related to handling of fpcast, > setval, and local variables that are not yet reflected in sparse code > so these tests will not pass yet in sparse. > > The tests that pass are here: > > https://github.com/dibyendumajumdar/dmr_c/tree/master/tests Again, sorry I am not able to response to it earlier. I am in the catching up backlog mode now. For those test case. I think it is very welcome to integrate into sparse. If you want, you can break them down to smaller, digestible piece and start submitting to sparse as patch series for review, or git pull request. It will not get pull into this release v0.5.1 for sure. We can start the discussion now. I can even have a post release branch doing the merges for the patches after the release. > These are not exactly in the format currently used for testing sparse. > It will be nice however to add all the test cases to the official > sparse repository. That is fine. If it is all just test cases, that is relative safe. Luc has a hue pile of pending patches I want to merge. If you touch some of those core components, which result in Luc need to fix up his repository a lot, then I would say hold a little bit for Luc's patches being merged. The test case should be more or less fine. Thank you 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
