PSA: Integration with IREE for multi-target and whole model compilation about iree-llvm-sandbox HOT 6 OPEN

cc @ftynse @Mogball @MaheshRavishankar @ThomasRaoux @stellaraccident @matthias-springer @gysit

from iree-llvm-sandbox.

+1 glad to see this getting bridged

from iree-llvm-sandbox.

What's the plan for moving changes between different projects? Let's say I factor out the interface into a separate dialect as proposed in the RFC.

from iree-llvm-sandbox.

@ftynse I'd say strongly favor doing this in core and we'll adopt.

If you need a tmp staging ground, it would be quite better to do it in iree-dialects given the coupling introduced by the integration.

If you must do it directly in the sandbox, we'll either pay the price of manually syncing into IREE or wait until upstreamed to core; depending on perceived cost/benefit.

from iree-llvm-sandbox.

+1 for things that we think may be "core bound" in some number of months, we make local choices aimed at limiting overhead. This can include a cross project dependency (ie. Sandbox to iree) or copying sub directories (ie. Iree-dialects was made to be "reused by cp" as a staging ground for things that may be core bound at some point).

If it looks like upstreaming something isn't going to happen, then if we still want it, we need to find it a better stable home.

from iree-llvm-sandbox.

The back and forth integration has now landed.

I added a new github action testing IREE integration on the iree/sandbox branch that is meant to be non-blocking for pushes.
The main github action remains the thing we should look out for remaining green and updates to iree/sandbox are on a best effort basis for now.

Please let me know if you see something that is cause of concern or experience unnecessary hardships so we can refine the process.

from iree-llvm-sandbox.