search for: cloog_found

.... I find this problem because I put a new testcase in test/Cloog/CodeGen/, but it is never executed. >> >> @Sebastian, you added the Cloog directory in r169159, including all testcases and the lit.local.cfg. The lit.local.cfg ensures that  cloog specific testcases are executed only with CLOOG_FOUND by adding the following lit commands in test/Cloog/lit.local.cfg: >> >>          cloog = config.root.cloog_found >> >>          if cloog not in ['TRUE', 'true'] : >> >>              config.unsupported = True >> >> However, there are tw...

...nd or not. I find this problem because I put a new testcase in test/Cloog/CodeGen/, but it is never executed. >> @Sebastian, you added the Cloog directory in r169159, including all testcases and the lit.local.cfg. The lit.local.cfg ensures that cloog specific testcases are executed only with CLOOG_FOUND by adding the following lit commands in test/Cloog/lit.local.cfg: >> cloog = config.root.cloog_found >> if cloog not in ['TRUE', 'true'] : >> config.unsupported = True >> However, there are two problems: >> First, since th...

...not. I find this problem because I put a new testcase in test/Cloog/CodeGen/, but it is never executed. > >> @Sebastian, you added the Cloog directory in r169159, including all testcases and the lit.local.cfg. The lit.local.cfg ensures that cloog specific testcases are executed only with CLOOG_FOUND by adding the following lit commands in test/Cloog/lit.local.cfg: > >> cloog = config.root.cloog_found > >> if cloog not in ['TRUE', 'true'] : > >> config.unsupported = True > >> However, there are two problems: >...

...og is found or not. I find this problem because I put a new testcase in test/Cloog/CodeGen/, but it is never executed. @Sebastian, you added the Cloog directory in r169159, including all testcases and the lit.local.cfg. The lit.local.cfg ensures that cloog specific testcases are executed only with CLOOG_FOUND by adding the following lit commands in test/Cloog/lit.local.cfg: cloog = config.root.cloog_found if cloog not in ['TRUE', 'true'] : config.unsupported = True However, there are two problems: First, since the cloog_found is set as "@CLOOG_FOUND@&quot...

...found or not. I find this problem because I put a new testcase in test/Cloog/CodeGen/, but it is never executed. > @Sebastian, you added the Cloog directory in r169159, including all testcases and the lit.local.cfg. The lit.local.cfg ensures that cloog specific testcases are executed only with CLOOG_FOUND by adding the following lit commands in test/Cloog/lit.local.cfg: > cloog = config.root.cloog_found > if cloog not in ['TRUE', 'true'] : > config.unsupported = True > However, there are two problems: > First, since the cloog_found is set...

Hi Tobi, Sebastian Pop wrote: > Another option is to disable these tests when cloog is not available, and to > write other tests that will work with -polly-codegen-isl. I think I like this way better. The attached patches move all the test dependent on Cloog to be conditionally executed to CLOOG_FOUND. I am preparing another patch that will adapt most of the current tests to work with ISL's code generator. Ok to commit? Thanks, Sebastian -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation -------------- next part -------------- A non-text...

Hi Tobi, when polly is configured with isl and without cloog, make polly-test does not pass cleanly as there are several testcases that use a pass flag that does not exist in this configuration: -polly-cloog. I was thinking to address this problem by renaming -polly-cloog and -polly-codegen-isl to -polly-codegen and making all these tests using -polly-codegen. Another option is to disable these

...rote: > > Another option is to disable these tests when cloog is not available, and to > > write other tests that will work with -polly-codegen-isl. > > I think I like this way better. The attached patches move all the test > dependent on Cloog to be conditionally executed to CLOOG_FOUND. I am preparing > another patch that will adapt most of the current tests to work with ISL's code > generator. See attached the patch that adds to the Isl/CodeGen all the tests that can be run also with the ISL code generator (the vectorizer tests cannot yet be executed with the ISL cod...

...her option is to disable these tests when cloog is not available, and to > > > write other tests that will work with -polly-codegen-isl. > > > > I think I like this way better. The attached patches move all the test > > dependent on Cloog to be conditionally executed to CLOOG_FOUND. I am preparing > > another patch that will adapt most of the current tests to work with ISL's code > > generator. > > See attached the patch that adds to the Isl/CodeGen all the tests that > can be > run also with the ISL code generator (the vectorizer tests cannot ye...

..._PACKAGE(Isl REQUIRED) FIND_PACKAGE(Gmp REQUIRED) FIND_PACKAGE(Cloog) FIND_PACKAGE(Pluto) with no cmake option to avoid executing... FIND_PACKAGE(Cloog) I have been deinstalling the fink cloog packages, so that cmake/FindCloog.cmake doesn't find the CLOOG_INCLUDE_DIR/CLOOG_LIBRARY and set CLOOG_FOUND TRUE, as well as passing cmake -DCLOOG_FIND_REQUIRED=0. It would be much cleaner if we had a cmake option that would prevent FIND_PACKAGE(Cloog) from executing in the toplevel CMakeLists.txt. Also, shouldn't the default for polly 3.4 be to disable Cloog so that it uses an isl-only build?...