Alexander Viand
Alexander Viand
This isn't urgent, so I'm happy to wait until Asra's back!
Pinging @asraa again on this :)
Re-opening this and adding "reducing build (disk) size" as a goal, as that's the sticking point for devcontainer.json/ default GH codespaces (see #1001). Building HEIR+LLVM using bazel requires around 25GB...
Looking through the bazel llvm setup, I noticed this comment. @j2kun any update on removing the NVPTX target? Also, I think it'd make sense to replace `X86` and `AArch64` with...
Also, where do we specify which parts of LLVM we want? I.e., what's the bazel equivalent of `-DLLVM_ENABLE_PROJECTS=mlir`?
Closing this as the upstream PR was merged (and now we've got `polynomial` "downstream" again anyway).
@asraa Do you have a fix in the works for this, or should I start looking at this?
> Ready for an initial review while I finish up tests. Given your most recent comment, do you still want (initial) reviews already, or should we wait until those issues...
> OK, fixed up all the tests. Last two things > > * Whether we should rename the "lazy" part to something closer to its actual behavior (maybe "optimize-relinearization"?) >...
> Hmmm. I think this will also break the CMake build because we don't yet have the ortools dependency in cmake, right? Yes, unfortunately. Though it looks like ortools is...