search for: isl_test

...rious conflicts with the generated configure > etc. files. However, due to the need of an isl-noexeceptions.h, I may > need to include such a cycle in isl-merge.py anyway. Can you clarify when/if autotools are required and under what circumstances. > > * Isl has its own unittest "isl_test.c". It is put into bin/ (but not > installed) and run by llvm-lit on llvm-check. This was just the > simplest to do since it doesn't require any additional lit.site.cfg in > order to find the isl_test in a different directory. Can it end up in the unittests subdirectory with the...

...e to different Autotools versions being installed on the different systems, this might lead to spurious conflicts with the generated configure etc. files. However, due to the need of an isl-noexeceptions.h, I may need to include such a cycle in isl-merge.py anyway. * Isl has its own unittest "isl_test.c". It is put into bin/ (but not installed) and run by llvm-lit on llvm-check. This was just the simplest to do since it doesn't require any additional lit.site.cfg in order to find the isl_test in a different directory. Looking forward for your feedback. Michael [1] http://isl.gforge...

...versions being installed on the different systems, > this might lead to spurious conflicts with the generated configure > etc. files. However, due to the need of an isl-noexeceptions.h, I may > need to include such a cycle in isl-merge.py anyway. > > * Isl has its own unittest "isl_test.c". It is put into bin/ (but not > installed) and run by llvm-lit on llvm-check. This was just the > simplest to do since it doesn't require any additional lit.site.cfg in > order to find the isl_test in a different directory. > > > Looking forward for your feedback. >...

...on the different systems, > > this might lead to spurious conflicts with the generated configure > > etc. files. However, due to the need of an isl-noexeceptions.h, I may > > need to include such a cycle in isl-merge.py anyway. > > > > * Isl has its own unittest "isl_test.c". It is put into bin/ (but not > > installed) and run by llvm-lit on llvm-check. This was just the > > simplest to do since it doesn't require any additional lit.site.cfg in > > order to find the isl_test in a different directory. > > > > > > Looking f...

..., > > > this might lead to spurious conflicts with the generated configure > > > etc. files. However, due to the need of an isl-noexeceptions.h, I may > > > need to include such a cycle in isl-merge.py anyway. > > > > > > * Isl has its own unittest "isl_test.c". It is put into bin/ (but not > > > installed) and run by llvm-lit on llvm-check. This was just the > > > simplest to do since it doesn't require any additional lit.site.cfg in > > > order to find the isl_test in a different directory. > > > > >...

...>> this might lead to spurious conflicts with the generated configure >>>> etc. files. However, due to the need of an isl-noexeceptions.h, I may >>>> need to include such a cycle in isl-merge.py anyway. >>>> >>>> * Isl has its own unittest "isl_test.c". It is put into bin/ (but not >>>> installed) and run by llvm-lit on llvm-check. This was just the >>>> simplest to do since it doesn't require any additional lit.site.cfg in >>>> order to find the isl_test in a different directory. >>>> &...

...versions being installed on the different systems, > this might lead to spurious conflicts with the generated configure > etc. files. However, due to the need of an isl-noexeceptions.h, I may > need to include such a cycle in isl-merge.py anyway. > > * Isl has its own unittest "isl_test.c". It is put into bin/ (but not > installed) and run by llvm-lit on llvm-check. This was just the > simplest to do since it doesn't require any additional lit.site.cfg in > order to find the isl_test in a different directory. > > > Looking forward for your feedback. >...