Jeremy Kun

I found a slightly better fix: adding `--deleted_packages=externals` to `.bazelrc`. Try updating to the latest commit of this repository and running `bazel build ...:all` again.

> The current SchemeInfoAnalysis annotates the `func` operation with the different types of `ops` that occur inside the function. The [SchemeSelectionAnalysis](https://github.com/Fraunhofer-AISEC/heir/blob/scheme_selection/lib/Analysis/SchemeSelectionAnalysis/SchemeSelectionAnalysis.cpp#L31-L34) is currently empty, because I can't get it to...

Adding the build file and otherwise it seems to work for me: ```bash $ bazel run //tools:heir-opt -- --annotate-scheme-info --debug --debug-only=SchemeInfo $PWD/tests/Examples/common/dot_product_8.mlir Visiting: arith.constant. Visiting: arith.constant. Visiting: tensor.extract. Visiting: tensor.extract....

Perhaps one thing to note is that the analysis won't "visit" your `func.func` directly because the data flow framework handles that by another means (initializing all the func args to...

I'm not sure I understand the problem. The function is annotated in the example above. What outcome are you trying to achieve?

Ah yes, you won't be able to do it in an analysis using the data flow framework. But you could just do the analysis work in the pass after the...

Ready for an initial review while I finish up tests. Also an open question for me: how should we document the mathematical formulation of the ILP? In a page on...

Discovered when writing more tests: - Rotate ops need to have linearized inputs, so this needs to be added as an additional constraint in the ILP - For some reason,...

I don't think the remaining issues will drastically change the structure of the PR, so it is ready for a first round of reviews.

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"?) - Where to put...