Open mikeseven opened 6 years ago
well, that was straightforward. I'll update my repo to submit a PR asap.
The distributed Tiramisu backend requires a specific branch of Halide but the other backends will work on up to date Halide without a problem.
@jrayzero and @psuriana is there anything in the distributed backend that still depends on the private branch ? Are we ready to move the public up-to-date Halide ?
@mikeseven does the public Halide and LLVM 6.0 work fine for you ? Do all tests succeed ?
yes all tests pass though I didn't build/test with MPI.
The changes I did are in tiramisu_codegen_halide.cpp for things like: Halide::Internal::Max::make(op0, op1, True); changed to Halide::Internal::Max::make(op0, op1);
For ISL, it is just updating to new version 0.20. And LLVM/CLANG updating to release_60.
Before doing that, for Halide, I didn't see differences with @jrayzero tiramisu_64bit branch and Halide code when the clone was done around December last year. I may have missed something for distributed Tiramisu?
Tiramisu has dependencies with LLVM/Clang 5 because Halide branch is outdated. The same could be said with ISL to be updated to 0.20.
Any idea when this updated alignment would occur?