How to use ClangIR downstream?

[keryell]

How to use ClangIR downstream?

[lanza]

Hey @keryell!

We rebase because upstream LLVM doesn't use merges. The goal is to, at some point, be integrated into the main LLVM tree.

The rebase cadence is rather discontinuous right now. I hope to get it more regular soon, but have been busy with other work. A weekly cadence is the eventual goal.

How do other projects work with ClangIR?

An example sycl-clangir branch is available. I took the git merge-base upstream/main intel/sycl-mlir point, rebased clangir to that and then merged the intel/sycl-mlir branch. I think VAST just builds the clangir-17 branch as their base branch and then builds VAST against it.

[keryell]

sorry I didn't had the time to catch up with your during the meeting, and thanks for trying out ClangIR.

Do not worry and thank you for making ClangIR. :-)

Hopefully upstreaming would make it more appealing to you.

Sure, more appealing to anyone indeed!

[bcardosolopes]

@keryell sorry I didn't had the time to catch up with your during the meeting, and thanks for trying out ClangIR. Hopefully upstreaming would make it more appealing to you. I don't know if this helps, but we also track the base LLVM branch from latest rebases in https://github.com/llvm/clangir/tree/base, so that would a common ancestor to look at.

[keryell]

We rebase because upstream LLVM doesn't use merges. The goal is to, at some point, be integrated into the main LLVM tree.

I guess this depends on whether the up-streaming happens soon or not.

An example sycl-clangir branch is available. I took the git merge-base upstream/main intel/sycl-mlir point, rebased clangir to that and then merged the intel/sycl-mlir branch.

Interesting.
I have done the same and it seems going quite better than I would have expected, with only 1 commit keryell@ba06c76 to have the compilation working.
Not perfect, since running check-clang-cir shows 32 failed tests among 221.