Ashay Rane
Ashay Rane
Based on last night's run, here's the green LLVM commit for this week: ec5def5e20f6ae9fe8cc30e5ee152d4b239e1e95. However, MHLO is just a tad behind this commit, causing the Torch-MLIR and ONNX-MLIR build to...
@joker-eph Thanks, if you could create a branch, that'd be great. I'm a bit worried that managing an extra branch might get cumbersome, but I'm happy to try it and...
@joker-eph For patches required to MHLO to work with new LLVM commits, in addition to pushing them to a branch in the MHLO repo, I'm happy send PRs (that can...
Thanks @stellaraccident, that's a great idea, assuming the multitude of branches in the MHLO repo isn't a problem.
Edit: I realized that if we were to run `git gc`, then commits outside of branches (and thus, presumably unreachable) would be removed from the repo. At the risk of...
Thanks @powderluv, I see the reason for the branch now. The green LLVM commit for this week is 061e0189a3dab6b1831a80d489ff1b15ad93aafb.
@joker-eph Since I don't have the permission to rename protected branches, could you rename the `greencommit` branch to `greencommit/2022-08-04-ec5def5` please? That would accomplish two things: 1. preserve the commit hash...
Yes, pushing to a new branch works, but that'd change the commit hash, thus breaking commits from last week where we used the old commit hash.
Sorry, the usual CI run failed. Marking as draft while I diagnose and fix the problem.
Rebasing to see if PR https://github.com/llvm/torch-mlir/pull/1218 resolves the build failure.