|
| 1 | +[中文版](./release_notes_v0.2.0_cn.md) |
| 2 | + |
| 3 | +## FlagTree 0.1.0 Release |
| 4 | + |
| 5 | +### Highlights |
| 6 | + |
| 7 | +FlagTree inherits capabilities from the previous version, continuously integrates new backends, expands support for Triton versions, and provides hardware-aware optimization capabilities. The project is currently in its early stages, aiming to be compatible with existing adaptation solutions for various AI chip backends, unify the code repository, build a code co-construction platform, and quickly implement multi-backend support in a single repository. |
| 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, 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 | +Jointly developing common extensions for the middleware layer with backend vendors, and open-sourcing standardized PyTorch backend extensions to support Triton / FlagTree practices. <br> |
| 16 | + |
| 17 | +* Dual Compilation Path Support |
| 18 | + |
| 19 | +Supports TritonGPU and Linalg compilation paths. Provides multiple integration paradigms for non-GPGPU backends, adds FLIR repository support for Linalg Dialect extensions and MLIR extensions for backend compilation. |
| 20 | + |
| 21 | +* Added support for Triton versions |
| 22 | + |
| 23 | +Currently supported Triton versions include 3.0.x, 3.1.x, __3.2.x__, __3.3.x__, with __bold__ indicating newly added ones. |
| 24 | + |
| 25 | +* Hardware-aware optimization support |
| 26 | + |
| 27 | +Supports providing guided programming interfaces for backend-common or specific hardware features. Through compatible extensions, adding guidance information at the frontend to provide flexibility in operator writing and performance tuning. |
| 28 | + |
| 29 | +* Joint construction with FlagGems operator library |
| 30 | + |
| 31 | +Collaborating with the [FlagGems](https://github.com/FlagOpen/FlagGems) operator library to support related features in version adaptation, backend interfaces, registration mechanisms, and test modifications. |
| 32 | + |
| 33 | +### Looking ahead |
| 34 | + |
| 35 | +GPGPU backend code will be integrated, decoupling backend differentiation changes from TritonGPU; non-GPGPU backends will be horizontally integrated on the FLIR foundation, with unified design for common passes. <br> |
| 36 | +Providing Triton adaptation version upgrade guides for backend vendors: 3.0 -> 3.1 -> 3.2 -> 3.3. <br> |
| 37 | +CI/CD will add FlagGems operator library functional testing. <br> |
| 38 | +Integrating C++ Runtime functionality to reduce runtime overhead outside of kernels to be on par with CUDA. <br> |
0 commit comments