Replies: 1 comment 2 replies
-
We discussed two aspects of this in the last meeting. First was that the more solid/standardized parts of the project would be upstreamed to MLIR. Second, internally Google has an on-call rotation to fix upstream breakages of internal projects. Because HEIR has a "google-internal" source of truth, we can argue that we should be added to the list of "critical" projects to be updated (currently it is on a list of "best effort" updates). Adding in the fact that maintaining this repo will be a critical part of my full time job, I'm hoping this can ease the burden of maintenance for the rest of the community. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello, it appears that the HEIR project consistently merges LLVM (MLIR) from upstream.
I wonder if we can continue doing this after starting to implement MLIR dialects. Based on my experience, the MLIR project undergoes rapid changes, occasionally overlooking backward compatibility.
Certainly, I acknowledge the significance of staying up-to-date with upstream developments. Nevertheless, I would appreciate hearing others' opinions while considering the maintenance costs involved.
Beta Was this translation helpful? Give feedback.
All reactions