On Sat, Aug 12, 2017 at 3:44 PM, Dibyendu Majumdar <mobile@xxxxxxxxxxxxxxx> wrote: > > I have a native MSVC build - I'd rather not have to rely upon mingw / > cygwin. I can understand that. > Windows 10 now has a Linux subsystem - I am planning to do my > Linux builds within that. But I would rather have a test harness that > runs natively on all platforms. I can understand that also but: - if you want to validate the IR, it's something that is platform independent and if validated on your linux platform it will be valid for the others too - the script used to run the test is something very simple, it shouldn't take much work to write a version in some other language. Making this new version *the* official version is something else and rewritting all the testcases so that this or that is easier for this new version would be a totally different question, of course. > > Being able to run it is an easy way to verify that the test works - > because the success / failure condition is part of the test itself / > or output produced by the test. Ideally though I would like to be able > to validate the Sparse IR - but don't know an easy way to do this > other than comparing the output from linearizer. Slowly, it's what I'm already doing in the current testcases. It's far from ideal but we can already progress. >> One thing I want to have for testing linearized code is a simulator >> for sparse's IR. It's even something quite easy (or at least straightforward) >> to do. At least once you can associate to each phi-node's 'argument' the >> parent BB they come from. This is something I'm planning to do for several >> reasons. > > Do you mean you will have a VM that runs Sparse IR? That would be nice > but it is a lot of effort I would think. Yes. I call that a simulator but it's all the same. It would be a program that take some input file (either directly the C source or the IR in some format yet to defined) and will 'execute' the IR instruction. It's in fact something very easy to do, something like a weekend project, *once* we associate parent BB to phi-node's 'arguments'. This BB for phi-node's arg is something very needed and it's the top of my todo list but for the moment, there is more important things to fix. -- Luc -- 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
