Running "different tests" on cmake based test-suite build

Hello Friends,

With configure based build deprecated on llvm, how can I run different tests/pass on the suite ()?

Right now I am having a hacky solution, which includes running the “still present” configure file of test-suite to generate the MAKE..Makefile;

cd external-testsuite-build-loc

/project/test-suite/configure --enable-optimized -disable-assertions

but while running ‘make TEST=PASS’ I am getting error for trying to include $(LLVM_OBJ_ROOT)/Makefile.config which is obviously not there on a cmake based llvm build. I have to edit the generated makefile to bypass this.

Can you please point me to some clean solution or let me know if am missing something?

Hi Sandeep,

The CMake version of the test-suite has been improved (see https://reviews.llvm.org/D21360) so that it’s easy to plug additional test suites. A starting point would be to look at how the TEST_SUITE_SUBDIRS variable in the top level CMakeLists.txt is used.

Kind regards,

Arnaud

I think this bug report is about adding new programs to the test suite. I don’t think Sandeep is asking how to add more test programs to the test suite; he is asking how to add new Makefiles to the test suite to make it run new experiments that it did not run previously. As context, several previous research projects used an interface within the old autoconf test suite to extend it to compile programs with different compiler options and run performance experiments on them. For example, the SAFECode and Automatic Pool Allocation projects added rules to compile and run programs with additional transforms and to record the results in CSV files which could be imported into other programs for creating graphs for papers. All of this could be done without modifying any files within the test-suite project; one simply created additional Makefiles, set come variables on the make command line, and fired off the experiments with “make.” I believe Sandeep is asking whether similar functionality exists within the new Cmake build system and, if so, how to use it. I am curious, too. It would make running some experiments for my research projects more convenient. I just assumed this feature was deprecated as I got the impression that I was the only one still using it. Regards, John Criswell

Hello All
As John rightly pointed out, my question is about adding the capability to build the testsuite differently and not about how to add other testsuites.
For example before configure build were deprecated, we can do something like make TEST=mypass, to build the testsuite according to the makefile rules in TEST.mypass.Makefile and that was handy if we want to test out own passes on the testsuite. To achieve the same in the current cmake build system, I need to do a hack solution as mentioned in my first post. Is there any clean way to achieve the same.

Thanks
Sandeep

Just as an aside, as far as running a custom pass on testsuite, one solution that I was using is to configure testsuite using

cmake CC=

where my_own_script might contain something like: clang -Xclang -load -Xclang mypass.so “$@”

Nevertheless, the previous “make TEST=mypass” solution was much more handy in term of the different ways you can build or report the results.