On 10 August 2017 at 23:50, Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx> wrote: > On Thu, Aug 10, 2017 at 10:44 PM, Dibyendu Majumdar > <mobile@xxxxxxxxxxxxxxx> wrote: >> >> Yes, the current arrangement is a stop gap. As I develop both on >> Windows and Linux, I need a portable solution so I cannot really use >> shell scripts. > > People use bash with mingwin, for example. Would it be something > usable for you? > I have a native MSVC build - I'd rather not have to rely upon mingw / cygwin. 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. >>> Another question is that, I don't know how many your test get impact >>> by the llvm versions. If it get tight to a specific version of llvm, the >>> test case has less value. People will get false positives due to different >>> llvm version. > > If it begin to be the case we'll need to add a new tag telling to ignore > the test if version this or that. > >> The tests are all designed to be runnable > > I think this is very very important. > Of course, you're interested in LLVM output but not only. > 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. > 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. 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
