FlagOS Daily Intelligence Report (2026-10-15)
Research window: 2026-10-14 06:00 ~ 2026-10-15 06:00 (Beijing time, approx. 24 hours; Thursday morning report, window counted from the cutoff of the previous daily report (10-14)).
Sources: GitHub (org: flagos-ai, full verification of pushed_at across 61 repos, verification of 68 commit searches, retrieval and verification of 62 merged PRs and 226 open PRs, atomic verification of Releases across 26 repos and tags across 7 repos, org event stream and branch-level supplementary verification), Google News RSS (24 sets of Chinese and English query terms, via proxy), HN Algolia, Tavily supplementary retrieval (MetaX / Tsingmicro official releases and conference dispatches verified via original sites), CSDN column and BAAI community verification (see appendix source list for details).
Issue Index
- Today’s Highlights: MiniCPM-V 4.7 achieves Day-0 across twelve FlagOS platforms (MetaX / Tsingmicro released the same night); 11 FEPs opened in one night for the 2.3 cycle; organization creates 4 new repos on the same day (10-14)
- I. Open-Source Project Progress (GitHub Activity)
- 1.1 Organizational Cadence: 26 repos pushed, 68 commits, 62 merges; new FlagCV and audio trio repos created (10-14)
- 1.2 Release Engineering: 2.3 cycle FEP batch submission — 11 FEPs covering inference, training, compiler, and deployment (10-14)
- 1.3 Torch-FL: Two new backends — Apple Silicon (Metal) and Iluvatar BI-V150; failed operators batch-routed to cpu_fallback (10-14)
- 1.4 FlagGems: KernelGen Nvidia ten-operator batch, KMCompiler fix line, and kunlunxin batch-2 merged (10-14)
- 1.5 FlagTree: PPU fp32 GEMM merged, MTHREADS TLE two-in-a-row, and FlagMega fix under review (10-14)
- 1.6 Inference Stack: sglang-plugin-FL Iluvatar fused operators merged; vllm-plugin-FL / FlagGems-vllm advancing on multiple fronts (10-14)
- 1.7 FlagCX: Two UIL merges, unified CI framework landed; Tsingmicro backend PR opened (10-14)
- 1.8 Release Engineering & Governance: build-infra runtime dynamic FlagTree version selection; community contributor data three-in-a-row (10-14)
- 1.9 Other Lines: FlagQuantum / FlagPrism / FlagScale / FlagDNN / FlagTrain / Trident / FlagSparse (10-14)
- II. News Coverage & Ecosystem
- 2.1 MiniCPM-V 4.7 Day-0 across twelve FlagOS platforms: MetaX / Tsingmicro release and validation the same night (10-13 ~ 10-14)
- 2.2 MetaX x SGLang Meetup: Three parties discuss upstream co-building of SGLang Plugin (10-14)
- 2.3 Conference Preview: Main forum to cover FlagOS 2.2, six sub-forums and hands-on workshops (10-14)
- 2.4 Search & Official Channel Verification: Zero hits on component lines; no new articles on CSDN homepage (10-14)
- III. Member Unit Deep Dive
- 3.1 MetaX: MiniCPM-V 4.7 dual-spec Day-0 (42nd model cumulative) and SGLang Meetup (10-14)
- 3.2 Tsingmicro: Dual-spec Day-0 and precision alignment; FlagCX backend PR opened (10-14)
- 3.3 Kunlunxin: XPU3 approval in progress; batch-2 performance batch and xpu3.6 CI merged (10-14)
- 3.4 Iluvatar: Torch-FL BI-V150 backend three-in-a-row and inference operators merged (10-14)
- 3.5 Ascend & Zhenwu PPU: Ascend fix batch merged and under review; PPU CI integration landed (10-14)
- 3.6 Moore Threads / Hygon / Enflame / DAMO XuanTie et al.: Multi-line maintenance and review (10-14)
- IV. Summary & Trend Observations
- Appendix: Source Verification Table
- Complete Source List
Today’s Highlights: MiniCPM-V 4.7 Achieves Day-0 Across Twelve Platforms via FlagOS (MetaX / Tsingmicro Release Same Day); 11 FEPs Filed Overnight for the 2.3 Cycle; Organization Creates 4 New Repos in One Day (10-14)
Date: 2026-10-13 ~ 2026-10-15 Sources: MetaX (MiniCPM-V 4.7 Day-0, 10-14) · Tsingmicro (reprint of original, 10-14) · community #140 · community #139 · Torch-FL #516 · FlagCV (see appendix for full list)
- MiniCPM-V 4.7 Day-0 Across Twelve Platforms: On 10-13, ModelBest and OpenBMB jointly open-sourced the on-device multimodal model MiniCPM-V 4.7 (dual specs: 35B-A3B MoE and 1B; the 35B-A3B is the first open-source MoE capable of lossless, smooth on-device operation, using ~3GB memory at 13+ token/s); the FlagOS community completed cross-chip Day-0 adaptation across twelve platforms (built on the vLLM-plugin-FL inference plugin, with the roster including DAMO XuanTie, NVIDIA, Hygon, Kunlunxin, MetaX, Iluvatar CoreX, Tsingmicro, Enflame, and others). MetaX released an official post on 10-14: leveraging Xiyun C-series GPUs and the MXMACA software stack, it completed full-pipeline Day-0 validation for both specs (its 42nd model cumulatively), and extended both specs to ARM on-device CPU platforms; Tsingmicro released an official post on 10-14: dual-spec deployment validation and precision alignment (Math_500 / GPQA_Diamond / MMLU_Pro aligned with NVIDIA native baselines). Adaptation images were simultaneously published to the FlagRelease organizations on ModelScope / HuggingFace (see 2.1).
- Batch FEP Submissions for the 2.3 Cycle: From 10-14 22:35 to 10-15 01:49 (Beijing time), community opened 11 FEP PRs in a row (#139 ~ #149) — offline one-click installer (runtime + app Python-layer self-extracting package), vLLM 0.28 ten-platform compatibility, SGLang 0.5.18 upgrade and DeepSeek-V4 W8A8, Compressor calibration quantization (GPTQ / AWQ / AutoRound), LightX2V multi-chip generation plugin, Megatron three-model multi-platform training, Megatron ViT co-located training, TransformerEngine upstream plugin migration, TE Triton / CUDA FSA backends, Torch-FL coverage and execution capabilities, Torch-FL Iluvatar platform support — the first wave of submissions ahead of the 2.3 FEP merge deadline (11-13) (see 1.2).
- Engineering-Side Hardware Footprint Expansion: The organization created 4 new repos on the same day — FlagCV (computer vision) and kaldi-triton / puAudioAnalysis-sino / librosa-sino (speech and audio analysis line), all placeholder-created with LICENSE (10-14 10:35 ~ 14:23); Torch-FL merged two new accelerator paths — the Iluvatar BI-V150 “FlagGems-primary” backend (#514) and the Apple Silicon Metal runtime foundation (#516, the 11th accelerator); across the organization, 26 repos received pushes within the window and 62 PRs were merged (see 1.1 / 1.3).
Assessment: This window marks a day of dual-track progress — “ecosystem collaboration + cycle engineering.” On-device model Day-0 has evolved from a single-model adaptation event into a pipeline of cross-member collaboration (two member organizations spontaneously published official validation posts the same day + a twelve-platform roster + FlagRelease images), while the 2.3 cycle entered its substantive submission phase with 11 FEPs in a single night; combined with 4 new repos (expansion into vision / speech domains) and new Torch-FL backends, the organization is filling out the 2.3 feature landscape at the pace of a final sprint before the conference (10-17 / 18).
I. Open Source Project Progress (GitHub Activity)
1.1 Organizational Cadence: 26 Repos Pushed, 68 Commits, 62 Merges; New FlagCV and Audio Trio Created (10-14)
Date: 2026-10-14 Source: org: flagos-ai repository list · FlagCV · kaldi-triton · librosa-sino · org repos API (verification baseline)
- Total org repositories 57 → 61: 26 repos had pushes within the window (docs, build-infra, FlagGems-Experimental, FlagCX, Torch-FL, FlagDNN, FlagGems, FlagGems-sglang, community, FlagAttention, FlagGems-vllm, sglang-plugin-FL, FlagTree, FlagQuantum, FlagTrain, TransformerEngine-FL, FlagScale, FlagPrism, Trident, vllm-plugin-FL, FlagSparse, release-info, plus 4 new repos); commit search returned 68, merged PRs 62 (17 repos), in-review PR updates 226 — the org maintained its high-intensity cadence from the week before the conference.
- 4 new repos created (10-14): FlagCV (10:35) — computer vision line; kaldi-triton (14:21), puAudioAnalysis-sino (14:22), librosa-sino (14:23) — Kaldi speech recognition and audio analysis line. All four currently contain only LICENSE placeholders (no README on either web or raw), following the optest (10-13) precedent — a domain-expansion signal of “repo first, content later.”
- No new Releases / tags within the window: the latest tags remain FlagTree
0.7.1a1+xpu3.6(10-13 16:36) and FlagGemsv5.5.0.dev0(10-12); atomic checks of releases across 26 repos and tags across 7 repos found no additions within the window. - Org event stream (100 events): PullRequestEvent 65, PushEvent 15, CreateEvent 7, IssueCommentEvent 6, DeleteEvent 4, Review 3; end-of-window activity comprised the community FEP batch (10-14 22:35 ~ 10-15 01:49, 11 events), two FlagCX Dependabot events (10-15 02:20 / 02:22), two FlagGems-Experimental Dependabot events (10-15 02:51 / 02:54), and build-infra #1345 (10-15 05:14).
1.2 Version Engineering: 2.3 Cycle FEP Batch Submission — 11 FEPs Covering Inference, Training, Compiler, and Deployment (10-14)
Date: 2026-10-14 ~ 2026-10-15 Source: community #139 · #140 · #141 · #142 · #143 · #144 · #145 · #146 · #147 · #148 · #149 (full list in appendix)
- Submission cadence: #139 (22:35) opened by tengqm, the remaining 10 (#140 ~ #149) densely opened by wbavon within three minutes from 10-15 01:46 ~ 01:49; all are single-file additions (+79 ~ +255 lines), currently mergeable=True, in review — against the 2.3 timeline disclosed last period (FEP merge deadline 11-13), the first submission wave arrived on schedule.
- Inference side: FEP-0140 vLLM multi-version platform compatibility (ten domestic vendor platforms on vLLM 0.28 + closing 0.24 compatibility and release acceptance gaps, including versioned plugin artifacts, dependency matrix, and inference / serving acceptance); FEP-0141 SGLang platform upgrade and model support (release / test matrix for the 0.5.18 upgrade, 0.5.11 / 0.5.12 Empty-mode extension, DeepSeek-V4 W8A8 inference).
- Training side: FEP-0144 Megatron three-model multi-platform training (Qwen3.5-27B, Qwen3.5-35B-A3B, DeepSeek-V4-Flash-Base, covering numerical correctness, optimizer updates, checkpoint resume, and paired performance); FEP-0145 Megatron ViT co-located training (CSA / HCA / DSA integration and placement checks); FEP-0146 TransformerEngine upstream plugin migration (from TE-FL to upstream TE + standalone versioned FL plugin, including activation, initialization-failure fallback, checkpoint migration, and rollback); FEP-0147 TE Triton and CUDA FSA backends (capability-gated dispatch, independent output / gradient references, kernel and model benchmarks).
- Deployment and generation: FEP-0139 offline one-click installer (install runtime + app Python layer on air-gapped hosts via self-extracting package, pinned to the same configs.yaml as the image); FEP-0142 Compressor calibration quantization and deployment (GPTQ / AWQ / native AutoRound + reproducible calibration, per-module precision policy, and hardware profiling); FEP-0143 LightX2V multi-chip generation plugin (NVIDIA + five domestic vendors for image / video generation, defining model / device coverage, wheel packaging, generation quality, and native baseline performance).
- Framework side: FEP-0148 Torch-FL coverage and execution capabilities (HF architecture coverage across seven domestic platforms, FlagGems C++ dispatch, low-bit dtype emulation (Beta), and FSDP2 optimization experiments); FEP-0149 Torch-FL Iluvatar platform support (device runtime, operator dispatch, model execution, and reproducible wheel builds).
1.3 Torch-FL: Two New Backends — Apple Silicon (Metal) and Iluvatar BI-V150; Failed Operators Batch-Routed to cpu_fallback (10-14)
Date: 2026-10-14 Source: Torch-FL #516 · #514 · #518 · #517 · #519 (full list in appendix)
- #516 (merged 23:59, +2083/-35, 38 files) “native Apple Silicon (Metal) backend”: adds the 11th accelerator
mpsto torch-fl — running the PrivateUse1 (flagos) device on Apple M-series GPUs via Metal; this change includes only the runtime foundation (device / stream / event / memory + caching allocator), with no operators registered yet — a “11th platform” placeholder for local development and CI scenarios. - #514 (merged 13:47, +3805/-40, 25 files) Iluvatar (BI-V150 / Tianshu) “FlagGems-primary” backend: full scaffolding of the iluvatar build platform (PR text discloses AI Agent collaboration and human review process); #518 (merged 20:26, +284/-139) routes the 37 FlagGems operators that failed on BI-V150 to cpu_fallback — same-day “onboard + stop-loss” loop.
- Supporting merges: #517 (17:48) single-sources the FlagGems integration test suite across all platforms; #505 (20:02) aligns the integration pipeline; #334 (23:23) caches pip downloads in the integration line; #513 (11:13) makes CI fail fast on unreachable indexes and prioritize CPU-torch images.
- Three in-review PRs (opened same day): #519 converges per-platform pipelines into a config-driven matrix; #520 makes CUDA boxing an explicit switch and moves CUDA-ABI platforms toward FlagGems-primary; #521 adds “selective platform CI + trusted maintainer control” — the next stage of institutionalizing multi-platform CI.
1.4 FlagGems: KernelGen Nvidia Ten-Operator Batch, KMCompiler Fix Line, and kunlunxin batch-2 Merged (10-14)
Date: 2026-10-14 Source: FlagGems #6999 · #7006 · #6662 · #7081 · PR list (full list in appendix)
- 25 merges, highest in the org: KernelGen Nvidia ten-operator batch (
_reshape_copy#6999, grid_sampler #7006, atleast_3d #7022, special_modified_bessel_i1 #5293, mH #6995, dstack #7039, glu_jvp #6991, geqrf #7002, istft #6982, select_copy #7007); test hygiene batch (sparse index-copy value range narrowing #7102, metadata query dtype cross-reduction #7130, duplicate test cleanup #7137 / #7148 / #7154); KMCompiler fixes (Thead / MetaX linalg_matrix_power #7050, MetaX fp16 rnn_tanh precision #6971, Ascend replication_pad2d_backward coreDim capping #7081, Ascend unsafe_index_put grid capping #7033); CI and docs (robust-checkout #7071, device-visibility contribution guide #7063). - kunlunxin three PRs: batch-2 performance batch #6662 merged (all_dim and batch_norm pass the 0.8x threshold, adaptive_avg_pool2d_backward override, fix for import-time global side effects, +1443/-260); #7067 updates flagtree for xpu / iluvatar and standardizes the ops-test notification helper; #7153 ports the XPU
copy_/sortfix on master back to the fix_backends_bug branch. - High-density in-review lines: llaboon’s XPU3 series keeps refreshing (#7095 ~ #7116, concentrated updates around 18:07 that evening); SiliconFlow batch (#6941 scatter_reduce launch limits / PPU path, #7069 upsample_nearest2d_backward performance, #7016 convolution_backward, #6940 argsort timeout); bin913 four fixes (#7158 all / any strided, #7159 zero_ strided, #7160 sub / div 0-dim scalar, #7161 exponential_ tail rate correction); Ascend three PRs (#7149 embedding_spmdm, #7157 zeros / zero_ fix GIL crash, #7134 correctness and FlagTree compatibility); MetaX #7145 (remove cudnn_convolution implementation); MTHREADS #7163 (index_put N=1 scatter-write mapping optimization).
1.5 FlagTree: PPU fp32 GEMM Merged, MTHREADS TLE Double, and FlagMega Fixes in Review (10-14)
Date: 2026-10-14 Source: FlagTree #1360 · #1267 · #1268 · #1361 · #1366 (full list in appendix)
- 5 merges: PPU fp32 AIU GEMM memory-order support with tests #1360 (the fix landing point for issue #1359 last period); MTHREADS TLE double #1267 (SQMMA lowering, layout inference, shared addressing, and PH1 partition sync fix) + #1268 (static CTA alignment extract_tile skips shared scratch); FlagMega CP-SAT search acceleration #1361 (producer / reshard index convergence); CI #1366 adds FlagGems baseline and test workflow for xpu3.6 (echoing build-infra package releases and the Torch-FL kunlunxin line).
- In review: two FlagMega fixes (#1373 Qwen3 vLLM profile re-inference slice dtype, #1374 qkv_rope_with_cache add grid barrier before sequence advance); #1372 tle_raw.call tensor fragment parameter example; #1353 CommonIR conversion integration on enflame / hcu / iluvatar / metax / mthreads; #1352 TileIR upgrade to CUDA Tile IR 13.4; #1348 PPU swizzled TLE layout preservation; #1294 MThreads persistent GEMM pipeline and SPMC sync; #1278 warp-specialize body inline DSL; AMD / Ada five-PR series (#1363 / #1364 / #1365) keeps refreshing.
- Tag line: no new build tags within the window (latest is
0.7.1a1+xpu3.6, 10-13).
1.6 Inference Stack: sglang-plugin-FL Iluvatar Fused Operators Merged; vllm-plugin-FL / FlagGems-vllm Multi-Line Progress (10-14)
Date: 2026-10-14 Source: sglang-plugin-FL #132 · vllm-plugin-FL #579 · #594 · FlagGems-vllm #912 (full list in appendix)
- sglang-plugin-FL #132 merged (16:40): implements Iluvatar fused operators for sglang 0.5.18 — echoing the 2.2-line SGLang upgrade (FEP-0141).
- vllm-plugin-FL: #579 merged (11:31, Iluvatar multi-attention cache binding fix, avoiding the NotImplementedError of the vLLM 0.24 upstream cache binder); in-review line #585 (vLLM 0.28 adaptation for kunlunxin P800), #583 (Flaggems-vllm introduction), #581 / #592 (three-stage CI and 0.4.0-dev workflow rework), #593 (op profile adds eager reference), #594 (MetaX staging machine self-healing, labeled “debug / never merge”, still active at 10-15 06:01).
- FlagGems-vllm #912 merged (11:17): adds
--base-dataparameter and supports comparison against CUDA baseline (+72550/-5, 7 files, including baseline data); #926 in review (MTHREADS FlagTree 0.7 FP8 varlen attention optimization). - FlagGems-sglang #156 merged (14:55): introduces ops-test workflow (aligned with the ops-test line of FlagAttention / FlagGems).
1.7 FlagCX: Two UIL Merges, Unified CI Framework Landed; Tsingmicro Backend PR Opened (10-14)
Date: 2026-10-14 Source: FlagCX #650 · #654 · #652 · #656 (full list in appendix)
- #654 merged (10:44): shared engine adds result-aware transfer state API (pending / success / actual error, rejecting unknown or cross-connection transfer IDs).
- #652 merged (15:07): coalesced batch holds the group guard throughout — fixes premature guard release within the batching window.
- #650 merged (22:39, +864/-9, 14 files): unified CI framework — config-driven platform discovery + per-platform Feishu notifications; FlagCX had no existing per-platform workflows and no trigger conflicts, a “clean landing.”
- #656 opened (19:30, +128/-20, 8 files): Tsingmicro support for the FlagOS backend — a communication library backend contribution from a new member unit (see 3.2); additionally #657 / #658 (CRL: IBRC visibility flush, multi-segment VMM symmetric window) opened that evening, #643 (Hygon Device API / IR CI) keeps updating, #659 / #660 are Dependabot.
1.8 Release Engineering and Governance: build-infra Dynamically Selects FlagTree Version at Runtime; community Contributor Data Triple (10-14)
Date: 2026-10-14 Source: build-infra #1341 · #1342 · #1344 · community #136 · #137 · #138 (full list in appendix)
- build-infra three merges: #1342 (13:43) uses
FLAGTREE_VERSIONto dynamically select the FlagTree version at container startup — FlagTree releases frequently, so this avoids rebuilding all upper-layer images on every bump; #1341 (20:59) migrates FlagTree package publishing to self-hosted runners (stated reason: hosted runners access Nexus at only tens of KB/s, and four upload attempts of the 263 MB deb and 87 MB rpm failed); #1344 refreshes the 2.3.0 image description (bot). - community contributor data triple (13:01 / 14:59 / 17:54): #136 adds 15 FlagTree contributors and three organizations (Sunrise (Xiwang), T-Head, NVIDIA); #137 adds vendor backend contributors for FlagCX + TransformerEngine-FL; #138 adds FlagGems confirmed contributors (BAAI employees / interns + vendors) — 2.3 community metrics data continues to fill in.
- docs: ModelScope documentation update #551 (10-14 17:02, +5373/-69, 31 files, bot); model library #542 updated through 10-15 05:32. release-info: the gh-pages release info site maintains pushes (pushed_at 10-14 14:12), with no new Release objects within the window.
1.9 Other Lines: FlagQuantum / FlagPrism / FlagScale / FlagDNN / FlagTrain / Trident / FlagSparse (10-14)
Date: 2026-10-14 Source: FlagQuantum #626 · FlagPrism #16 · FlagScale #1300 · FlagTrain #11 · Trident #3 (full list in appendix)
- FlagQuantum: workshop documentation line advances (#626 merged: bit-order convention explanation + bilingual circuit diagrams, 22 files; paired with 4 docs / test commits the same day).
- FlagPrism: architecture design document merged #16 (+484: English architecture guide — source → IR instrumentation → runtime recording → analysis / debug reports, including 4 SVG diagrams and Profiler / Debugger chapters).
- FlagScale: PPU platform incorporated into the shared CI pipeline and CUDA TE-FL dependency preparation improvements #1300 merged (+1540/-18, 34 files); #1308 in review (Qwen3.5 multimodal training sequence packing, +899).
- FlagDNN: three “add equivalent performance” PRs (Ascend 11:19 / MTHREADS 15:23 / DAMO XuanTie 23:02) — equivalent performance data rolling out across multiple backends.
- FlagTrain: #14 merged (Ascend backend CI), #11 merged (packbits operator, Nvidia + Ascend); #18 in review (fp8_gemm).
- FlagAttention: #96 merged (ops-test format alignment + Enflame operator list path fix).
- FlagGems-Experimental: five KernelGen merges #665 / #674 / #680 / #685 / #689 (_fw_primal_copy, sparse_compressed_tensor, sparse_bsc_tensor, cartesian_prod, coalesce); #730 / #731 are Dependabot.
- Trident: #2 / #3 test operator batch (+2829 and +285; #2 closed, #3 in review) — torch operator coverage tests for the TVM FFI bridge.
- FlagSparse: #110 / #111 packaging and CI handling (shiptux: license tabularization to fit distro setuptools, packaging workflow changed to verify-only).
- TransformerEngine-FL / Megatron-LM-FL: #134 merged (unified CI framework + removal of eight per-platform duplicate triggers); #136 in review (NPU vendor capability query and tensor scaling fix); Megatron-LM-FL #201 (unified CI framework) keeps updating.
II. News Coverage and Ecosystem
2.1 MiniCPM-V 4.7 Achieves Day-0 Support Across Twelve Platforms via FlagOS: MetaX / Tsingmicro Publish Validation the Same Evening (10-13 ~ 10-14)
Date: 2026-10-13 ~ 2026-10-14 Source: MetaX (Corporate News) · Tsingmicro (Original Reprint) · ModelBest (Zhihu Post) · 10jqka (MetaX Mirror) (full list in appendix)
- On 10-13, ModelBest and OpenBMB released MiniCPM-V 4.7 (dual specs: 35B-A3B and 1B; 35B-A3B is the first open-source MoE capable of lossless, smooth on-device execution, requiring ~3GB memory and achieving 13+ token/s decoding; SRFT self-replay fine-tuning also open-sourced), achieving Day-0 coverage across twelve platforms via Zhongzhi FlagOS on the day of release (built on the vLLM-plugin-FL inference plugin; platform list includes DAMO XuanTie, NVIDIA, Hygon, Kunlunxin, MetaX, Iluvatar CoreX, Tsingmicro, Enflame, etc.); adapted images are available on the FlagRelease organization on ModelScope / HuggingFace.
- MetaX Official Release 10-14: Leveraging Xiyun C-series GPUs and the MXMACA full-stack software suite, completed Day-0 full-pipeline adaptation and inference validation for both specs, with both specs extended to ARM edge CPU platforms; cumulative Day-0 support for 42 mainstream models; MXMACA is compatible with 40+ AI frameworks, 1000+ models, and 6000+ open-source project tests, with full support for PyTorch 2.8’s 2410 GPU operators; the model incorporates DSpark speculative decoding adaptation.
- Tsingmicro Official Release 10-14: Deployment validation and precision alignment for both specs (Math_500, GPQA_Diamond, MMLU_Pro aligned against NVIDIA native versions as baseline); reconfigurable dataflow architecture combined with FlagGems enables rapid coverage of both dense attention and GDN / SSM linear attention structures; also reviewed the recent Day-0 list (DeepSeek-V4, Hy3, Qwen3.8 series, GLM5.3-Flash, MiniCPM5-2B, Xing4.0-29B, etc.).
2.2 MetaX x SGLang Meetup: MetaX / SGLang / FlagOS Discuss Plugin Upstream Co-Development (10-14)
Date: 2026-10-14 Source: MetaX (Corporate News) (full list in appendix)
- MetaX and the SGLang community co-hosted an AI Infra Meetup (five talks: KV Cache optimization, TTFT / TPOT metrics, CXL pooled memory and PD disaggregation, Mooncake distributed KV cache and production-grade cluster deployment).
- Tripartite technical exchange: During the Meetup, MetaX, SGLang, and FlagOS held in-depth discussions on the approach of “SGLang supporting different chip vendors through the Plugin mechanism,” initially forming a roadmap for advancing SGLang Plugin open-source upstream, and clarifying subsequent collaborative co-development methods—echoing three parallel efforts: the same-day merge of sglang-plugin-FL #132 (Iluvatar fused operators, sglang 0.5.18) and FEP-0141 (SGLang platform upgrade).
2.3 Conference Highlights: Main Forum to Interpret FlagOS 2.2, Six Sub-Forums and Hands-On Workshops (10-14)
Date: 2026-10-14 Source: iyiou (reprinted from “Yejie”) · Conference Registration Page (full list in appendix)
- Two days before the conference (10-17 / 18, Beijing Zhongguancun National Independent Innovation Demonstration Zone Exhibition Center): highlights updated—the main session will present and deeply interpret FlagOS 2.2 (“from token economy to physical AI” evolution path, compute evolution in the trillion-token era, next-generation AI foundation and the “debate of the decade” roundtable).
- Six sub-forums (AI Systems / Quantum-Intelligence Fusion / Embodied Intelligence / AI Agent / Automotive Intelligence / International AI Computing Cooperation) and hands-on workshops (KernelGen automatic operator generation, edge deployment, Triton-TLE novel Attention kernel, FlagScale-Agent) cover the complete pipeline “from operator generation to edge deployment”; the conference features BAAI SoulAgent “Help Me Listen” AI note-taking service across all forums; registration is open.
2.4 Search and Official Channel Verification: Zero Hits on Component Lines; No New Articles on CSDN Homepage (10-14)
Date: 2026-10-14 Source: Google News RSS (24 sets of Chinese and English queries, via proxy) · HN Algolia · CSDN Column · BAAI Community
- Google News RSS: 24 query sets yielded 14 hits; 2 events included (MiniCPM-V 4.7 member articles see 2.1, conference highlights see 2.3); excluded: Houmo AI ecosystem conference open-source article (edge AI software stack, not FlagOS-related), Enflame “A-share listing” article (09-11 original repost), MetaX X302 award and CIIF retrospective articles (10-12, excluded by semantics in previous issue), BAAI Community general AI reposts and market articles. Direct component name searches (FlagGems / FlagScale / FlagTree / FlagCX / KernelGen, etc.) yielded zero hits in the 24-hour window.
- HN Algolia: 8 query sets (4-day window) no direct hits; CSDN Column: homepage articles remain from late August (no new articles in window); BAAI Community: no entries detected in window.
- Complementary verification: MiniCPM-V 4.7 and conference highlights verified item-by-item via Tavily search and member company official sites (metax-tech.com); additionally cross-validated with 10jqka mirror and CSDN blog reprint (blog.csdn.net/weixin_72169639).
III. Deep Dive on Member Organizations
3.1 MetaX: MiniCPM-V 4.7 Dual-Spec Day-0 (42nd Cumulative Model) and SGLang Meetup (10-14)
Date: 2026-10-14 Source: MetaX #12668 · MetaX #12666 (full list in appendix)
- Day-0 numbers: Dual-spec full-stack adaptation (Xiyun C series + MXMACA), both specs extended to ARM edge CPUs; 42 cumulative Day-0 models (full range of text / multimodal / OCR / image generation); MXMACA covers 40+ frameworks, 1000+ models, 6000+ open-source project tests, and full support for all 2410 GPU operators in PyTorch 2.8.
- Community collaboration: Three-party Plugin upstream discussion at SGLang Meetup (see 2.2); CNCC 2026 (10-22 to 24, Chengdu) attendance preview released the same day (two special sessions, two major booths).
- Engineering side: MetaX line reviews and fixes continued throughout the day (FlagGems #7145 removes cudnn_convolution implementation, #6950 quantized operators, vllm-plugin-FL #594 staging self-healing; see 1.4 / 1.6 for details).
3.2 Tsingmicro: Dual-Spec Day-0 and Precision Alignment; FlagCX Backend PR Opened (10-14)
Date: 2026-10-14 Source: Tsingmicro (original article repost) · FlagCX #656 · community #136 (full list in appendix)
- Day-0 and precision alignment: Dual-spec (35B-A3B / 1B) deployment verification, with Math_500, GPQA_Diamond, and MMLU_Pro aligned to NVIDIA native baselines; reconfigurable dataflow architecture and FlagGems cover both dense attention and GDN / SSM linear attention structures.
- Deep co-building: First batch of chips adapted for FlagTree FLIR (jointly with Ascend and ARM AIPU, participating in the low-level definition of 76 Triton primitives and 103 FlagGems operators); recently co-open-sourced with BAAI the world’s first programming model for 3D compute chips, Open3D-PIMC (code now live in the open-source community); reconfigurable computing 3.0 and 3.5D compute-in-memory fusion roadmap.
- Engineering side: FlagCX #656 (tsingmicro support for FlagOS backend, 8 files) opened that evening — the first backend-level contribution on the communication library side; community governance data (#136) also recorded its contributors (e.g., XingZibo-666) in the same period.
3.3 Kunlunxin: XPU3 Reviews Continue; batch-2 Performance Batch and xpu3.6 CI Merged (10-14)
Date: 2026-10-14 Source: FlagGems #6662 · FlagTree #1366 · FlagGems #7156 · FlagGems #7153 (full list in appendix)
- Merged side: FlagGems batch-2 performance batch #6662 (all_dim / batch_norm pass the 0.8x threshold, adaptive_avg_pool2d_backward override); #7153 XPU
copy_/sortfix port; #7067 updates xpu / iluvatar flagtree; FlagTree #1366 xpu3.6 FlagGems baseline + test workflow. - In-review side: llaboon’s XPU3 series (#7095 ~ #7116) maintains high-density refresh; new fix #7156 (iand_scalar / ior_scalar / hsplit and foreach optimization); performance batches #7049 / #7114 / #7089; #6720 div_mode fix.
- Collaboration: Torch-FL #519 ~ #521 (CI matrixization, CUDA boxing explicitization) under review (see 1.3) — last period’s “XPU3 batch consolidation” has shifted in this window to “institutionalization of performance and CI baselines.”
3.4 Iluvatar CoreX: Torch-FL BI-V150 Backend Triple and Inference Operator Merges (10-14)
Date: 2026-10-14 Source: Torch-FL #514 · Torch-FL #518 · sglang-plugin-FL #132 · vllm-plugin-FL #579 (full list in appendix)
- Runtime layer: #514 merges Iluvatar (BI-V150) “FlagGems-primary” backend (+3805/-40, 25 files); #518 routes 37 empirically failing operators to cpu_fallback (+284/-139) — same-day “onboarding + stop-loss” closed loop; #517 makes the FlagGems integration suite a single source across platforms.
- Inference layer: sglang-plugin-FL #132 (sglang 0.5.18 Iluvatar fused operators) and vllm-plugin-FL #579 (multi-attention cache binding fix) merged the same day.
- Compiler side: FlagTree ILUVATAR specialization and CommonIR integration line (#1353 includes iluvatar target) continue to advance.
3.5 Ascend and Zhenwu PPU: Ascend Fix Batch Merged and In Review; PPU CI Integration Landed (10-14)
Date: 2026-10-14 Source: FlagGems #7081 · FlagGems #7149 · FlagScale #1300 · FlagTree #1360 (full list in appendix)
- Ascend merged: FlagGems #7081 (replication_pad2d_backward coreDim cap fix), #7033 (unsafe_index_put grid cap); FlagTrain #14 (Ascend backend CI), #11 (packbits, covering Nvidia and Ascend).
- Ascend in review: #7149 (embedding_spmdm operator), #7157 (zeros / zero_ added to
CUSTOMIZED_UNUSED_OPS, fixing vLLM multi-process GIL crash), #7134 (operator correctness and FlagTree compatibility fix), #7069 (upsample_nearest2d_backward performance). - Zhenwu PPU: FlagScale #1300 PPU platform merged into shared CI (+1540/-18); FlagTree #1360 (PPU fp32 AIU GEMM) merged, #1348 (swizzled layout preservation) in review — the PPU line has moved forward one step from last period’s “CI updating.”
3.6 Moore Threads / Hygon / Enflame / DAMO XuanTie et al.: Multi-Line Maintenance and Reviews (10-14)
Date: 2026-10-14 Source: FlagTree #1267 · FlagCX #643 · FlagGems #7077 · FlagDNN commits (full list in appendix)
- Moore Threads: FlagTree MTHREADS TLE two consecutive merges (#1267 / #1268); #1294 (persistent GEMM pipeline) and FlagGems #7163 (index_put scatter-write mapping), FlagGems-vllm #926 (FP8 varlen attention) in review; FlagDNN adds mthreads equivalent performance data.
- Hygon: FlagCX #643 (Hygon Device API / IR CI testing) keeps updating; MiniCPM-V 4.7 Day-0 platform list includes Hygon.
- Enflame: FlagGems #7077 (ENFLAME update batch) keeps updating (18:31); FlagAttention #96 fixes Enflame operator list path merged.
- DAMO XuanTie: FlagDNN commit “add equivalent performance for thead” (10-14 23:02); community governance data (#136) adds T-Head organization; MiniCPM-V 4.7 Day-0 platform list includes XuanTie (see 2.1).
- Sunrise / CIX: Newly added to governance data organizations (Sunrise (曦望), #136) and entered the MiniCPM-V 4.7 Day-0 platform list.
- Cambricon / Horizon: No substantive activity on GitHub or news side in this window.
IV. Summary and Trend Observations
1. On-device Day-0 is moving from “isolated events” to a “pipeline”: On the day MiniCPM-V 4.7 was released, FlagOS achieved twelve-platform coverage with vLLM-plugin-FL; MetaX (42 models cumulative) and Tsingmicro each published official validation posts that same evening — the collaboration mechanism of “model release → multi-chip Day-0 → member-unit self-validation posts” has stabilized into a mature pattern, and Day-0 capability itself has become a narrative asset for member units externally.
2. The 2.3 cycle has entered the substantive submission phase: Eleven FEPs (#139 ~ #149) in a single evening cover inference (vLLM 0.28 on ten platforms, SGLang 0.5.18), training (Megatron three models / ViT), compiler migration (TE upstream plugin + FSA backend), deployment (offline installer), and generation (LightX2V) — against the FEP merge deadline of 11-13, the density of this first submission wave is notable; the next thing to watch is the FEP review and merge cadence.
3. “Platform matrixization” on the engineering side is accelerating: Torch-FL merged two new accelerator paths in a single day (BI-V150 FlagGems-primary, Apple Silicon MPS) and routed 37 failing operators to cpu_fallback the same day; the CI layer (Torch-FL #519 ~ #521, FlagCX #650, TE-FL #134) is converging toward “configuration-driven + single entry point” — the multi-platform maintenance cost problem is being systematically dismantled.
4. Domain expansion signals: vision and speech: Four repos created in one day (FlagCV + kaldi-triton / puAudioAnalysis-sino / librosa-sino) continue the optest pattern of “create the repo first, fill in content later”; combined with the existing FlagDNN / FlagSparse / FlagAudio lines, the component landscape for the 2.3 cycle shows signs of expanding from “large-model operators” to “multi-domain operators / toolchains.”
5. Next observation points: Review and merge of FEPs #139 ~ #149; first content submissions for the 4 new repos; Torch-FL CI matrixization (#519 ~ #521) and the merge cadence for FlagMega AMD/Ada and Qwen3 profile fixes; on-site announcements at the conference (10-17 / 18) (FlagOS 2.2 offline debut) and the first daily report after the conference; the first landing point of SGLang Plugin upstream co-building.
Appendix: Source Verification Table
| Source | Verification Method | Result |
|---|---|---|
| GitHub | org repos API (window pushes) | 61 repos in full; 26 repos pushed within the window; 4 new repos (details in 1.1) |
| GitHub | Commit search (committer-date) | 68 hits, categorized by repo and verified one by one |
| GitHub | Merged PR search (is:merged) | 62 PRs across 17 repos; details in 1.2 ~ 1.9 |
| GitHub | Open PR search (is:open) | 226 updates; top 100 verified one by one (mainly FlagGems 47 / community 11 / FlagTree 11) |
| GitHub | Tag / Release atomic verification | 26 repos’ releases + 7 repos’ tags; no new tags / new Releases within the window |
| GitHub | Event stream and branch-level supplement | 100 org events verified; FlagSparse #110/#111, Trident #2/#3, docs #551, release-info pushes verified one by one |
| News | Google News RSS (24 sets of Chinese and English query terms, via proxy) | 14 hits: 2 events included (MiniCPM-V 4.7, conference highlights); the rest excluded (non-FlagOS articles, republished old news, market articles) |
| News | Tavily supplementary search | Member-unit original posts (MetaX / Tsingmicro) and conference highlights verified one by one against the original sites |
| Community | HN Algolia | 8 sets of queries rechecked; no direct hits |
| Official channels | CSDN column / BAAI community | No new articles within the window on the column homepage; no entries within the window detected in the BAAI community |
| Historical comparison | 10-14 daily report (previous issue) | Deduplication verification: the previous issue covered through 10-14 06:00; all items in this issue are later than that cutoff (MiniCPM-V 4.7 is a cross-period event, not included in the previous issue) |
Complete Source List
- [1] Today’s highlights and 1.1 Organization overview — https://github.com/orgs/flagos-ai/repositories · https://api.github.com/orgs/flagos-ai/repos · https://github.com/flagos-ai/FlagCV · https://github.com/flagos-ai/kaldi-triton · https://github.com/flagos-ai/puAudioAnalysis-sino · https://github.com/flagos-ai/librosa-sino
- [2] 1.2 / Today’s highlights 2.3 cycle FEP batch — https://github.com/flagos-ai/community/pull/139 · https://github.com/flagos-ai/community/pull/140 · https://github.com/flagos-ai/community/pull/141 · https://github.com/flagos-ai/community/pull/142 · https://github.com/flagos-ai/community/pull/143 · https://github.com/flagos-ai/community/pull/144 · https://github.com/flagos-ai/community/pull/145 · https://github.com/flagos-ai/community/pull/146 · https://github.com/flagos-ai/community/pull/147 · https://github.com/flagos-ai/community/pull/148 · https://github.com/flagos-ai/community/pull/149
- [3] 1.3 / 3.4 Torch-FL — https://github.com/flagos-ai/Torch-FL/pull/513 · https://github.com/flagos-ai/Torch-FL/pull/514 · https://github.com/flagos-ai/Torch-FL/pull/516 · https://github.com/flagos-ai/Torch-FL/pull/517 · https://github.com/flagos-ai/Torch-FL/pull/518 · https://github.com/flagos-ai/Torch-FL/pull/505 · https://github.com/flagos-ai/Torch-FL/pull/334 · https://github.com/flagos-ai/Torch-FL/pull/519 · https://github.com/flagos-ai/Torch-FL/pull/520 · https://github.com/flagos-ai/Torch-FL/pull/521
- [4] 1.4 FlagGems merge batch — https://github.com/flagos-ai/FlagGems/pull/6999 · https://github.com/flagos-ai/FlagGems/pull/7006 · https://github.com/flagos-ai/FlagGems/pull/7022 · https://github.com/flagos-ai/FlagGems/pull/5293 · https://github.com/flagos-ai/FlagGems/pull/6995 · https://github.com/flagos-ai/FlagGems/pull/7039 · https://github.com/flagos-ai/FlagGems/pull/6991 · https://github.com/flagos-ai/FlagGems/pull/7002 · https://github.com/flagos-ai/FlagGems/pull/6982 · https://github.com/flagos-ai/FlagGems/pull/7007 · https://github.com/flagos-ai/FlagGems/pull/7102 · https://github.com/flagos-ai/FlagGems/pull/7130 · https://github.com/flagos-ai/FlagGems/pull/7137 · https://github.com/flagos-ai/FlagGems/pull/7148 · https://github.com/flagos-ai/FlagGems/pull/7154 · https://github.com/flagos-ai/FlagGems/pull/7050 · https://github.com/flagos-ai/FlagGems/pull/6971 · https://github.com/flagos-ai/FlagGems/pull/7081 · https://github.com/flagos-ai/FlagGems/pull/7033 · https://github.com/flagos-ai/FlagGems/pull/7071 · https://github.com/flagos-ai/FlagGems/pull/7063 · https://github.com/flagos-ai/FlagGems/pull/6662 · https://github.com/flagos-ai/FlagGems/pull/7067 · https://github.com/flagos-ai/FlagGems/pull/7153
- [5] 1.4 / 3.1 / 3.6 FlagGems under review — https://github.com/flagos-ai/FlagGems/pull/7095 · https://github.com/flagos-ai/FlagGems/pull/7099 · https://github.com/flagos-ai/FlagGems/pull/7100 · https://github.com/flagos-ai/FlagGems/pull/7101 · https://github.com/flagos-ai/FlagGems/pull/7103 · https://github.com/flagos-ai/FlagGems/pull/7104 · https://github.com/flagos-ai/FlagGems/pull/7105 · https://github.com/flagos-ai/FlagGems/pull/7107 · https://github.com/flagos-ai/FlagGems/pull/7109 · https://github.com/flagos-ai/FlagGems/pull/7110 · https://github.com/flagos-ai/FlagGems/pull/7111 · https://github.com/flagos-ai/FlagGems/pull/7112 · https://github.com/flagos-ai/FlagGems/pull/7116 · https://github.com/flagos-ai/FlagGems/pull/6941 · https://github.com/flagos-ai/FlagGems/pull/7069 · https://github.com/flagos-ai/FlagGems/pull/7016 · https://github.com/flagos-ai/FlagGems/pull/6940 · https://github.com/flagos-ai/FlagGems/pull/7158 · https://github.com/flagos-ai/FlagGems/pull/7159 · https://github.com/flagos-ai/FlagGems/pull/7160 · https://github.com/flagos-ai/FlagGems/pull/7161 · https://github.com/flagos-ai/FlagGems/pull/7149 · https://github.com/flagos-ai/FlagGems/pull/7157 · https://github.com/flagos-ai/FlagGems/pull/7134 · https://github.com/flagos-ai/FlagGems/pull/7145 · https://github.com/flagos-ai/FlagGems/pull/6950 · https://github.com/flagos-ai/FlagGems/pull/7163 · https://github.com/flagos-ai/FlagGems/pull/7156 · https://github.com/flagos-ai/FlagGems/pull/7049 · https://github.com/flagos-ai/FlagGems/pull/7114 · https://github.com/flagos-ai/FlagGems/pull/7089 · https://github.com/flagos-ai/FlagGems/pull/6720 · https://github.com/flagos-ai/FlagGems/pull/7077
- [6] 1.5 / 3.5 FlagTree — https://github.com/flagos-ai/FlagTree/pull/1360 · https://github.com/flagos-ai/FlagTree/pull/1361 · https://github.com/flagos-ai/FlagTree/pull/1267 · https://github.com/flagos-ai/FlagTree/pull/1268 · https://github.com/flagos-ai/FlagTree/pull/1366 · https://github.com/flagos-ai/FlagTree/pull/1373 · https://github.com/flagos-ai/FlagTree/pull/1374 · https://github.com/flagos-ai/FlagTree/pull/1372 · https://github.com/flagos-ai/FlagTree/pull/1353 · https://github.com/flagos-ai/FlagTree/pull/1352 · https://github.com/flagos-ai/FlagTree/pull/1348 · https://github.com/flagos-ai/FlagTree/pull/1294 · https://github.com/flagos-ai/FlagTree/pull/1278 · https://github.com/flagos-ai/FlagTree/pull/1363 · https://github.com/flagos-ai/FlagTree/pull/1364 · https://github.com/flagos-ai/FlagTree/pull/1365
- [7] 1.6 Inference stack — https://github.com/flagos-ai/sglang-plugin-FL/pull/132 · https://github.com/flagos-ai/vllm-plugin-FL/pull/579 · https://github.com/flagos-ai/vllm-plugin-FL/pull/585 · https://github.com/flagos-ai/vllm-plugin-FL/pull/583 · https://github.com/flagos-ai/vllm-plugin-FL/pull/581 · https://github.com/flagos-ai/vllm-plugin-FL/pull/592 · https://github.com/flagos-ai/vllm-plugin-FL/pull/593 · https://github.com/flagos-ai/vllm-plugin-FL/pull/594 · https://github.com/flagos-ai/FlagGems-vllm/pull/912 · https://github.com/flagos-ai/FlagGems-vllm/pull/926 · https://github.com/flagos-ai/FlagGems-sglang/pull/156
- [8] 1.7 / 3.6 FlagCX — https://github.com/flagos-ai/FlagCX/pull/650 · https://github.com/flagos-ai/FlagCX/pull/652 · https://github.com/flagos-ai/FlagCX/pull/654 · https://github.com/flagos-ai/FlagCX/pull/656 · https://github.com/flagos-ai/FlagCX/pull/657 · https://github.com/flagos-ai/FlagCX/pull/658 · https://github.com/flagos-ai/FlagCX/pull/643
- [9] 1.8 Release engineering and governance — https://github.com/flagos-ai/build-infra/pull/1341 · https://github.com/flagos-ai/build-infra/pull/1342 · https://github.com/flagos-ai/build-infra/pull/1344 · https://github.com/flagos-ai/build-infra/pull/1345 · https://github.com/flagos-ai/community/pull/136 · https://github.com/flagos-ai/community/pull/137 · https://github.com/flagos-ai/community/pull/138 · https://github.com/flagos-ai/docs/pull/551 · https://github.com/flagos-ai/docs/pull/542
- [10] 1.9 Other lines — https://github.com/flagos-ai/FlagQuantum/pull/626 · https://github.com/flagos-ai/FlagPrism/pull/16 · https://github.com/flagos-ai/FlagScale/pull/1300 · https://github.com/flagos-ai/FlagScale/pull/1308 · https://github.com/flagos-ai/FlagTrain/pull/14 · https://github.com/flagos-ai/FlagTrain/pull/11 · https://github.com/flagos-ai/FlagTrain/pull/18 · https://github.com/flagos-ai/FlagAttention/pull/96 · https://github.com/flagos-ai/FlagGems-Experimental/pull/665 · https://github.com/flagos-ai/FlagGems-Experimental/pull/674 · https://github.com/flagos-ai/FlagGems-Experimental/pull/680 · https://github.com/flagos-ai/FlagGems-Experimental/pull/685 · https://github.com/flagos-ai/FlagGems-Experimental/pull/689 · https://github.com/flagos-ai/Trident/pull/2 · https://github.com/flagos-ai/Trident/pull/3 · https://github.com/flagos-ai/FlagSparse/pull/110 · https://github.com/flagos-ai/FlagSparse/pull/111 · https://github.com/flagos-ai/TransformerEngine-FL/pull/134 · https://github.com/flagos-ai/TransformerEngine-FL/pull/136 · https://github.com/flagos-ai/Megatron-LM-FL/pull/201
- [11] 2.1 / 3.1 / 3.2 MiniCPM-V 4.7 Day-0 — https://www.metax-tech.com/ndetail/12668.html · https://www.163.com/dy/article/L980NQRP05389L1N.html · https://zhuanlan.zhihu.com/p/2093408613415109658 · https://m.10jqka.com.cn/20261014/c680696331.shtml · https://modelscope.cn/models/FlagRelease/MiniCPM-V-4.7-35B-A3B-BF16-tsingmicro-FlagOS · https://huggingface.co/FlagRelease/MiniCPM-V-4.7-35B-A3B-BF16-tsingmicro-FlagOS
- [12] 2.2 SGLang Meetup — https://www.metax-tech.com/ndetail/12666.html
- [13] 2.3 Conference highlights — https://www.iyiou.com/news/202610141143373 · https://www.bagevent.com/event/FlagOS2026
- [14] 2.4 Search and official channels — Google News RSS (24 sets of Chinese and English query terms, via proxy) · https://hn.algolia.com/ · https://flagos.csdn.net/ · https://hub.baai.ac.cn/
- [15] 3.6 Other units — https://github.com/flagos-ai/FlagTree/pull/1267 · https://github.com/flagos-ai/FlagTree/pull/1268 · https://github.com/flagos-ai/FlagTree/pull/1294 · https://github.com/flagos-ai/FlagCX/pull/643 · https://github.com/flagos-ai/FlagGems/pull/7077 · https://github.com/flagos-ai/FlagGems/pull/7163 · https://github.com/flagos-ai/FlagDNN/commits/master
- [16] Appendix verification baseline — https://github.com/flagos-ai · https://api.github.com/orgs/flagos-ai/repos · https://github.com/flagos-ai/FlagGems/tags · https://github.com/flagos-ai/FlagTree/tags