You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Release] Update flagtree version to v0.4.0, and add release notes (#276)
* [REPORT] Add release notes v0.4.0
* add content of tle-raw
Signed-off-by: Jinjie Liu <jjliu@baai.ac.cn>
* [REPORT] Update release notes v0.4.0 CN for hints
* Update release notes for Triton Language Extensions
* update further work for hints and tle-raw
* [REPORT] Update release notes v0.4.0 CN
* Add plans for TLE-Lite and TLE-Struct enhancements
* [DOC] Update readme for hints, tle wiki
* [DOC] Update readme for flagos
* [DOC] Update release notes en
* [Version] Update to v0.4.0
---------
Signed-off-by: Jinjie Liu <jjliu@baai.ac.cn>
Co-authored-by: Jinjie Liu <jjliu@baai.ac.cn>
Co-authored-by: i3wanna2 <15910307812@163.com>
Co-authored-by: sunnycase <sunnycase@live.cn>
FlagTree is an open source, unified compiler for multiple AI chips project dedicated to developing a diverse ecosystem of AI chip compilers and related tooling platforms, thereby fostering and strengthening the upstream and downstream Triton ecosystem. Currently in its initial phase, the project aims to maintain compatibility with existing adaptation solutions while unifying the codebase to rapidly implement single-repository multi-backend support. For upstream model users, it provides unified compilation capabilities across multiple backends; for downstream chip manufacturers, it offers examples of Triton ecosystem integration. <br>
5
+
FlagTree is part of [FlagOS](https://flagos.io/), a unified, open-source AI system software stack that aims to foster an open technology ecosystem by seamlessly integrating various models, systems and chips.
6
+
By "develop once, migrate across various chips", FlagOS aims to unlock the full computational potential of hardware, break down the barriers between different chip software stacks, and effectively reduce migration costs. <br>
7
+
FlagTree is an open source, unified compiler for multiple AI chips project dedicated to developing a diverse ecosystem of AI chip compilers and related tooling platforms, thereby fostering and strengthening the upstream and downstream Triton ecosystem.
8
+
Currently in its initial phase, the project aims to maintain compatibility with existing adaptation solutions while unifying the codebase to rapidly implement single-repository multi-backend support.
9
+
For upstream model users, it provides unified compilation capabilities across multiple backends; for downstream chip manufacturers, it offers examples of Triton ecosystem integration. <br>
6
10
Each backend is based on different versions of triton, and therefore resides in different protected branches. All these protected branches have equal status.
@@ -15,6 +19,7 @@ Each backend is based on different versions of triton, and therefore resides in
15
19
16
20
## Latest News
17
21
22
+
* 2026/01/08 Add wiki pages for new features [HINTS](https://github.com/flagos-ai/FlagTree/wiki/HINTS), [TLE](https://github.com/flagos-ai/FlagTree/wiki/TLE), [TLE-Raw](https://github.com/flagos-ai/FlagTree/wiki/EDSL).
18
23
* 2025/12/24 Support pull and install [Wheel](/README.md#non-source-installation).
19
24
* 2025/12/08 Added [enflame](https://github.com/FlagTree/flagtree/tree/triton_v3.3.x/third_party/enflame/) backend integration (based on Triton 3.3), and added CI/CD.
FlagTree inherits capabilities from the previous version, continuously integrates new backends, and strengthens the ecosystem. Building upon the foundation of creating a collaborative code-building platform and achieving single-repository multi-backend support, the project continues to develop unified backend specialization design, continues to build intermediate layer representation and transformation extensions (FLIR), enhances hardware-aware and compilation guidance support capabilities and scope (HINTS), and Extend the Triton language (TLE).
8
+
9
+
### New features
10
+
11
+
* Added multi-backend Support
12
+
13
+
Currently supported backends include nvidia, amd, triton_shared cpu, iluvatar, xpu, mthreads, metax, aipu, ascend, tsingmicro, cambricon, hcu, __enflame__, 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
+
* Added Triton version support
17
+
18
+
Added support for Triton 3.4 and 3.5, and established corresponding protected branches.
19
+
20
+
* Continuous development of FLIR
21
+
22
+
Ongoing expansion of Linalg intermediate layer representation and transformation extensions, and MLIR extensions to provide programming flexibility, enrich expression capabilities, and improve transformation capabilities. Established paradigm for multi-backend integration with FLIR, integrated ascend backend.
23
+
24
+
* FlagTree Backend Specialization Unified Design
25
+
26
+
FlagTree's unified backend specialization design aims to integrate backend integration paradigms, clearly manage backend specialization implementations, and provide an engineering foundation for backend adaptation to Triton version upgrades and migrations. For details, see [FlagTree_Backend_Specialization](/documents/decoupling/), which has been applied to backends such as iluvatar and ascend.
27
+
28
+
* Compilation Guidance: HINTS
29
+
30
+
Support for compilation guidance on shared memory + async copy on GPGPU, verified on the triton_v3.5.x branch. For more information, refer to [wiki](https://github.com/flagos-ai/FlagTree/wiki/HINTS).
31
+
32
+
* Triton Language Extensions: TLE
33
+
34
+
In response to the challenges facing Triton development, we propose TLE (Triton Language Extensions), which extends Triton at three levels to meet the urgent needs of users at different levels for operator programming languages. For details, see [wiki](https://github.com/flagos-ai/FlagTree/wiki/TLE).
35
+
36
+
**TLE-Lite** is a lightweight extension to Triton. All features are compatible with various hardware backends, requiring only minor modifications to existing Triton kernels to achieve significant performance improvements. Primarily targeted at algorithm engineers and rapid performance optimization scenarios.
37
+
38
+
**TLE-Struct** provides classified extensions (such as GPGPU, DSA) through hardware architecture clustering abstraction to meet further performance optimization needs. Requires developers to have some understanding of target hardware characteristics and optimization techniques.
39
+
40
+
**TLE-Raw** provides the most direct control over hardware, allowing the use of hardware vendors' native programming languages to achieve ultimate performance. Requires developers to have in-depth knowledge of target hardware, primarily targeted at performance optimization experts. For more information, refer to [wiki](https://github.com/flagos-ai/FlagTree/wiki/EDSL).
41
+
42
+
* Joint construction with FlagGems operator library
43
+
44
+
Collaborating with [FlagGems](https://github.com/FlagOpen/FlagGems) operator library on version compatibility, backend interfaces, registration mechanisms, and test modifications to support related features. FlagGems operator library has currently been adapted to Triton 3.5.
45
+
46
+
### Looking ahead
47
+
48
+
FLIR plans to integrate more backends, completing tsingmicro backend integration in Q1 2026.<br>
49
+
Protected branch triton_v3.4.x plans to integrate new backends.<br>
50
+
HINTS plans to optimize shared memory hints for GPGPU backends to better collaborate with existing Triton passes, while undergoing functional upgrades.<br>
51
+
TLE-Lite plans to extend Tensor slicing and distributed primitives.<br>
52
+
TLE-Struct plans to expose more hardware-related primitives and improve performance to approach hardware native languages.<br>
53
+
TLE-Raw plans to verify performance improvement opportunities in operators, optimize integration with Triton, while exploring other viable integration languages.<br>
0 commit comments