why design flow/stream/flow IR in IREE？

[mollon mollon]

have there any explain of why design flow/stream/hal IR for IREE？
In BladeDisc， there are just some dialect just describe ops and lower to GPU dialect or RAL IR，and final lib call， it‘s really simple，and compile faster，but in IREE ，abstract many complex IR（flow/stream/hal），is it overdesign？or To unify the software stack for cpu/gpu/npu/xpu/。。。？

[Scott Todd]

Hi, thanks for the question. A few of the presentations linked here discuss the design of flow/stream/hal: https://github.com/openxla/iree?tab=readme-ov-file#presentations-and-talks. Each stage has a purpose and splitting into stages helps with separating the concerns. Each stage is also generally designed so it can be bypassed by a user- or compiler- authored program.

On Tue, Jan 2, 2024 at 4:06 AM mollon mollon <guaigua...@gmail.com> wrote:

have there any explain of why design flow/stream/hal IR for IREE？
In BladeDisc， there are just some dialect just describe ops and lower to GPU dialect or RAL IR，and final lib call， it‘s really simple，and compile faster，but in IREE ，abstract many complex IR（flow/stream/hal），is it overdesign？or To unify the software stack for cpu/gpu/npu/xpu/。。。？

--
You received this message because you are subscribed to the Google Groups "iree-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to iree-discuss...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/iree-discuss/4464b43a-9c86-4a56-b8cf-b98fca499d7dn%40googlegroups.com.