|
| 1 | +<div align="right"><a href="./release_notes_v0.3.0_cn.md">中文版</a></div> |
| 2 | + |
| 3 | +## FlagTree 0.3.0 Release |
| 4 | + |
| 5 | +### Highlights |
| 6 | + |
| 7 | +FlagTree inherits capabilities from the previous version, continuously integrates new backends, and strengthens the ecosystem matrix. The project is currently in its early stage, aiming to be compatible with existing adaptation solutions for various chip backends, unify code repositories, create a collaborative code-building platform, and quickly achieve single-repository multi-backend support. Meanwhile, it continues to develop unified programming interface extensions, build intermediate layer representation and conversion extensions (FLIR), and enhance hardware awareness and compilation guidance support capabilities and scope (flagtree_hints). |
| 8 | + |
| 9 | +### New features |
| 10 | + |
| 11 | +* Added multi-backend Support |
| 12 | + |
| 13 | +Currently supported backends include triton_shared cpu, iluvatar, xpu (klx), mthreads, metax, aipu(arm npu), ascend npu & cpu, tsingmicro, cambricon, __hcu__, with __bold__ indicating newly added ones. <br> |
| 14 | +Each new backend maintains the capabilities of the previous version: cross-platform compilation and rapid verification, plugin-based high-differentiation modules, CI/CD, and quality management capabilities. <br> |
| 15 | + |
| 16 | +* Continuous integration with upstream ecosystems |
| 17 | + |
| 18 | +Thanks to the technical support from our partners, FlagTree has added compatibility with Paddle framework, OpenAnolis operating system, and Beijing Super Cloud Computing Center. |
| 19 | + |
| 20 | +* Continuous development of FLIR |
| 21 | + |
| 22 | +Ongoing expansion of DSL, TTIR extensions, Linalg intermediate representation and transformation extensions, and MLIR extensions to provide programming flexibility, enrich expression capabilities, and improve transformation capabilities. |
| 23 | + |
| 24 | +* Established compilation guidance specifications, added unified management module for multi-backend compilation |
| 25 | + |
| 26 | +flagtree_hints provides guidance for hardware unit mapping and compilation transformation optimization choices, and manages backend guidance differences through a unified module. |
| 27 | + |
| 28 | +* Joint construction with FlagGems operator library |
| 29 | + |
| 30 | +Collaborating with [FlagGems](https://github.com/FlagOpen/FlagGems) operator library on version compatibility, backend interfaces, registration mechanisms, and test modifications to support related features. |
| 31 | + |
| 32 | +### Looking ahead |
| 33 | + |
| 34 | +Improving GPGPU backend integration, decoupling backend specialization from main code implementation to establish an engineering foundation for FlagTree's general extensions and optimizations. <br> |
| 35 | +Aiming to comprehensively cover various implementation styles in the operator library, enhancing FLIR compilation completeness to match multiple backend requirements and enable compilation for more backends. <br> |
| 36 | +flagtree_hints will continue to explore operator performance optimization potential on different backends along both TritonGPU and Linalg compile-paths. <br> |
0 commit comments