fep(sig-edge): add Arm64 cpu backend to flagtree#15
Open
kevinzs2048 wants to merge 4 commits into
Open
Conversation
|
|
kevinzs2048
changed the title
JosephNew
reviewed
May 27, 2026
Per maintainer feedback, expand the FEP to include explicit reproduction steps in the Packaging and Test Plan sections, matching the format used by the vllm-plugin-FL FEP (see flagos-ai#23): * Packaging: 7-step build sequence (system deps, venv, optional manual LLVM, clone FlagTree, helper script, build, FlagGems install). * Test Plan: Environment Matrix + 3 verification phases (backend registration / operator-level rms_norm / end-to-end MiniCPM5-0.9B INT8 decode) each with executable commands and expected outputs. Full install reference lives in FlagTree#633 (documents/install_arm64.md).
kevinzs2048
force-pushed
the
sig-edge-arm64
branch
from
4b314f1 to
131bebd
Compare
- FlagGems merged: master (#3616) and 5.3.0-rc2 release branch (#3775); step 7 now clones flagos-ai/FlagGems -b 5.3.0-rc2 - C++ extension repo renamed flagos-ai/triton-cpu -> flagos-ai/flagtree-cpu; helper script is now link_flagtree_cpu.sh; install guide is install_cpu.md - FLAGGEMS_VENDOR=arm is now mandatory (arm device_query_cmd probe removed; import flag_gems fails without it) — added to the e2e run command - Verified build prerequisites: pybind11 (--no-build-isolation), TRITON_APPEND_CMAKE_ARGS to keep sleef out of /usr/local, export FLAGTREE_BACKEND=cpu for runtime kernel.s JIT
Reproduced the full packaging + test plan as a clean non-owner user: - Build install prefix: use per-user $HOME/.flagtree_install instead of the shared /tmp/flagtree_install. On a multi-user machine the shared dir is owned by whoever built first, so a second user's cmake --install fails with Permission denied (the very error the flag is meant to avoid). - Add 'pip install numpy' to step 2 to silence torch's 'Failed to initialize NumPy' warning (FlagGems pulls numpy anyway). Validated: clean test user passes Test 1 (10 create_cpu_* ops), Test 2 (rms_norm max err 0.014348745346069336), Test 3 (MiniCPM5-0.9B INT8, 169 INT8 Linears, TPS 18.19).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This FEP proposes adding Arm64 CPU as a supported backend for FlagOS, enabling FlagTree's Triton kernels and FlagGems operators to compile and run on Arm CPUs. The Arm64 TLE capabilities are organized as a standalone FlagTree plugin following existing plugin conventions, with Triton-CPU as the compiler substrate. This extends FlagOS's multi-backend compilation model from cloud-side accelerators to edge devices.
Status:
ProvisionalSIG: sig-edge
Target Version: FlagOS 2.1