Research window: 2026-11-03 04:30 ~ 2026-11-04 04:30 (Beijing time, past 24 hours; directly contiguous with the previous issue’s cutoff at 11-03 04:30).

Sources: GitHub key repository and organization push verification (RuyiAI-Stack, ruyisdk, openRuyi-Project, buddy-compiler; repository-by-repository verification of in-window commits, PRs, Releases, and tags for key repositories, plus organization-level push verification; upstream forks filtered by RISC-V / RVV / XuanTie keywords), ruyi package manager Releases and PyPI, packages-index, openRuyi packaging repository SPECS and PRs, RuyiSDK developer community forum, ruyiai-daily daily intelligence archive, three-page snapshot of the RuyiAI official homepage, openRuyi distribution news page, Google News RSS targeted Chinese and English queries (via proxy), arXiv search.

This Issue’s Index

  • Today’s Focus: openRuyi PR #1350 merged; the RuyiAI trio enters distro packaging seven weeks later (11-03)
  • I. RuyiAI Stack Progress (PyTorch / Triton / TileLang RISC-V porting)
    • 1.1 tilelang-riscv: eighteen-day silence broken; PR #5 merges TileOps streaming load and quantization paths (11-03)
    • 1.2 pytorch: zero commits in the riscv branch window; head commit swapped for yet another whole-branch replay of 81ecd427 (11-03 status)
    • 1.3 llvm-project: only one CI workflow change in the riscv branch window; A100/AME pipeline untouched (11-03)
    • 1.4 triton-riscv: zero commits on main; sixteen open PRs untouched (11-03 status)
  • II. RuyiSDK Toolchain and Distro
    • 2.1 The three specs in PR #1350: what versions buddy-mlir, triton-ruyiai, and tilelang-ruyiai each pin to (11-03)
    • 2.2 Version anchors: triton stuck at the 09-13 nightly, tilelang at 10-28, buddy at 0.1.2 (11-03)
    • 2.3 openRuyi clears its ledger the same day: seven PRs merged, packaging side occupies the whole day (11-03)
    • 2.4 ruyi main repo: zero commits, zero new tags; 0.54.0-beta.20261102 remains the only prerelease (11-03 status)
    • 2.5 openRuyi 2026.10 still missing; no November content on the news page (11-04 status)
  • III. Vector Extensions and Operator Optimization (VecIntrinBench / IntrinTrans / FBGEMM)
    • 3.1 The three vector repos remain silent; latest commits still at 02-13, 06-25, 07-13 (11-04 status)
    • 3.2 Operator work shifts to tilelang-riscv: 21 files, test surface expanded to streaming load and INT8/FP8 quantization (11-03)
  • IV. Buddy Compiler Updates
    • 4.1 buddy-mlir resumes commits; nightly 0.1.4.dev20261103 ships again (11-03)
    • 4.2 Distro spec pins 0.1.2, one patch behind the 0.1.3 release (11-03)
  • V. Community, Events, and Official Site
    • 5.1 Official site unchanged across three pages; two blog posts, twenty-three doc chapters (11-04 status)
    • 5.2 Forum adds a ruyi script installation guide; biweekly progress 080 still not out (11-03)
    • 5.3 ruyiai-daily 11-03 issue archived (11-03)
    • 5.4 Six external news queries yield no in-window hits; no relevant arXiv papers in window (11-04 status)
  • VI. Trend Observations
    • 6.1 From source builds to distro packages: the RuyiAI stack’s distribution path closes the last mile
    • 6.2 Packaging anchors lag upstream: the date in a version number is not the date of the code
    • 6.3 Two development lines resume the same day; ruyi mainline and openRuyi releases remain still

Today’s Highlight: openRuyi PR #1350 Merged — the RuyiAI Trio Enters Distro Packaging Seven Weeks Later (11-03)

Date: 2026-11-03　Sources: PR #1350 Add Ruyiai packages, three packaging commits, follow-up fix PR #1575

At 15:59 Beijing time on 11-03, PR #1350 was merged into the main openRuyi repository. The PR was opened at 17:55 on 09-21 and spent 43 days in review; it ultimately carried only three commits, ten files, and 838 added lines, yet it formally brought the hardest-to-distribute segment of the RuyiAI stack — the compiler backend and MLIR toolchain — into the distro’s SPECS directory.

The division of labor among the three packages is clear. buddy-mlir is the MLIR compilation framework, providing the dialects and passes needed for RISC-V vector (RVV) lowering; its spec declares 0.1.2, pins source to buddy-compiler commit 60f354a7, bundles an LLVM snapshot from RuyiAI-Stack/llvm-project (commit 3845a205), bootstraps with clang/lld 22, disables tests and Python packages, and installs the toolchain to /usr/lib64/buddy-mlir/llvm. python-triton-ruyiai (package name python-triton-riscv in the spec) combines upstream Triton commit 5889527 with the triton-riscv tag nightly/20260913-da5291b, and depends at runtime on buddy-mlir, buddy-mlir-llvm, and clang. python-tilelang-ruyiai (package name python-tilelang-riscv in the spec) pins tilelang-riscv commit 0b7d66eb and separately packages five submodules — TVM, dmlc-core, rang, tvm-ffi, and DLPack — at the versions fixed upstream; building it also requires python3dist(torch).

The patch contents reveal where distro adaptation ran into trouble: tilelang’s five patches respectively relax the apache-tvm-ffi upper bound to 0.1.11, drop the torch-c-dlpack-ext and patchelf build dependencies, make the toolchain look under /usr/lib64/buddy-mlir/llvm, skip z3 soname rewriting, and handle the libbacktrace switch for TVM FFI; triton’s two patches replace cmake/ninja/nanobind with system packages and add PATH plus /usr/lib64/buddy-mlir/llvm/bin lookup fallbacks for buddy-translate, buddy-llc, llc, and mlir-translate. In other words, the paths assembled from environment variables in the source tree must each be turned into reproducible lookup rules in the distro — that was the main workload of the 43-day review.

At 20:16 the same day, PR #1575 added one more fix: changing the #/ separator to / in Source0 and Source1 of buddy-mlir.spec, correcting the RPM source URL format. Another packaging bug was fixed the same day, confirming that the complexity of these three specs lies not in functionality but in packaging conventions and path details; the previous daily’s note that “the nineteen review comments centered on spec style” is now resolved here.

The significance of this merge is not in version numbers but in the distribution path. Previously, using the RuyiAI stack meant pulling triton-riscv, tilelang-riscv, and buddy-mlir yourself and setting variables like BUDDY_MLIR_BINARY_DIR per the docs; now that these three components exist in openRuyi’s packaging repo, once builds pass, users can install the same LLVM/MLIR chain the distro way, with versions, dependencies, and install layout fixed by the specs. The PR description also flags assisted tools (GLM-5.3, DeepSeek V4.1 Flash) per openRuyi’s AI contribution policy.

One caveat remains: the code pinned by all three specs predates current upstream. Packaging completion does not mean capability parity; see 2.2 for the specific gap.

I. RuyiAI Stack Progress (PyTorch / Triton / TileLang RISC-V Adaptation)

1.1 tilelang-riscv: Eighteen-day silence broken on day eighteen, PR #5 merges TileOps streaming load and quantization paths (11-03)

Date: 2026-11-03　Sources: PR #5, merge commit 57c548c, feature commit edd94c4, PR #4

Opened at 13:44, merged at 14:13 — a 29-minute interval. Submitted by laz174, this PR touches 21 files, +669/−112, and is tilelang-riscv’s first commit since 10-16’s “Build Python extension in Buddy CI,” ending eighteen days of silence.

The core change is in src/target/codegen_riscv.cc (+157/−1): it adds fallback helpers for streaming load on raw TileOps operators, plus FP32 __fdividef handling. The accompanying test surface is broad: new test_riscv_streaming_loads.py (+81) verifies byte fidelity, new test_riscv_ieee_arithmetic.py (+77) provides arithmetic regression, and new test_int8_quant.py (+83) covers INT8 quantization; five existing tests and the operator inventory are updated in sync:

  • test_int8_dequant.py (+20)
  • test_fp8_quant_per_block.py (+13/−3)
  • test_paged_kv_cache_write.py
  • test_elementwise_activations.py
  • operator_inventory.py (+9/−14)

On the docs side, docs/get_started/BuildOnSG2044.md is rewritten (+90/−34), machine-specific paths are removed from tilelang/tladapter/toolchain.py (+8/−11), and the Python extension’s ABI floor is aligned with supported versions.

After the merge, the main branch head is 57c548c. Two older PRs remain queued: #4 “RVV vector mask and max reduction lowering,” stalled since 09-28, and #2 “Add Codex-compatible RISC-V operator workflow,” stalled since 06-08; neither is merged.

1.2 pytorch: Zero commits on the riscv branch within the window, head replaced by another whole-branch replay at 81ecd427 (11-03 status)

Date: 2026-11-03 (status)　Sources: pytorch riscv branch, head commit 81ecd427

No new commits on the riscv branch within the window. The current head is 81ecd427, still with the message [SyncBots] Integrate PyTorch at 3afdbd3; committer time is 11-03 03:00 (Beijing time), author time 10-29 12:48, and the commit times of the branch’s twenty commits are rewritten into the same second — another whole-branch replay. This replay lands about 90 minutes before the start of this issue’s window; the previously recorded b20942de has been superseded, but the patch set is unchanged from last issue: Add riscv64 image locally (#51), Fix bytes_to_scalar for float/complex on RISC-V (#44), Scope linear cross entropy ULP tolerance to RISC-V (#42), inductor opinfo blocklist (#50), and earlier CI and tolerance changes.

The twenty upstream commits on main within the window (mean backward, cuDNN CTC, ROCm hipBLASLt, AOTI, dynamo, CODEOWNERS, etc.) are unrelated to this stack and are excluded per established convention. There is no new upstream sync record since the replay.

1.3 llvm-project: Only one CI workflow change on the riscv branch within the window, A100/AME chain untouched (11-03)

Date: 2026-11-03　Sources: llvm-project riscv branch, commit bef335e, PR #30, PR #31

At 11:57, the riscv branch added bef335e2 “[workflows] Use workflow-scoped token for PR rebases,” switching the token used by the PR rebase workflow from repository-scoped to workflow-scoped. It sits atop the 11-02 23:00 whole-branch replay (head 375bf3e4 at the time) and is automation maintenance, not a compiler change.

The two RuyiAI-stack-related commits on the branch remain: [RISCV] Lower IME intrinsics to SpacemiT A100 dot instructions (#30) and [RISCV] Add A100 HP/SP and pack/unpack lowering with calibrated scheduling (#31); below them is the chain formed by [AME] Update BOSC AME instructions (#29) and [RISCV] Update xtame design (#27) — “AME design → instruction definitions → intrinsics → lowering and scheduling.” This issue brings no additions to that chain, only an adjustment to the CI permission model.

1.4 triton-riscv: Zero commits on main, sixteen open PRs untouched (11-03 status)

Date: 2026-11-03 (status)　Sources: triton-riscv commit list, nightly list, PR #92, open PR list

The last commit on main is still the 10-31 13:15 dependency update (bumping the buddy-mlir anchor to nightly/v0.1.3.dev20261030). Zero commits and zero nightlies within the window; the latest nightly 2026-11-01-ed0ccd1 was published 11-02 16:32, before the window.

The open queue still holds sixteen. Rebase PR #92 (rebasing the integration onto official Triton v3.8.0) has not moved since its 11-02 21:43 refresh; the five “information-preserving” PRs #93 through #97 are stalled between 10-31 and 11-01; #85 (softmax and matmul optimization), last refreshed 10-30, remains the only entry in the queue directly aimed at performance. Main has therefore seen no new operator capability land since 10-31.

II. RuyiSDK Toolchain and Distributions

2.1 The three specs in PR #1350: which versions buddy-mlir, triton-ruyiai, and tilelang-ruyiai each target (11-03)

Date: 2026-11-03　Source: buddy-mlir.spec, python-triton-ruyiai.spec, python-tilelang-ruyiai.spec

The actual anchors of the three specs are as follows, all verifiable directly in the main repo:

  • buddy-mlir 0.1.2: Source0 points to buddy-compiler commit 60f354a7 (commit message “[ci] Add the publish-models workflow #925”), Source1 points to RuyiAI-Stack/llvm-project commit 3845a205; bootstrapped with clang/lld 22, BUDDY_ENABLE_TESTS=OFF, BUDDY_MLIR_ENABLE_PYTHON_PACKAGES=OFF, BUDDY_DOWNLOAD_CLI11=OFF, static library build, LLVM prefix installed to /usr/lib64/buddy-mlir/llvm.
  • python-triton-ruyiai 3.8.0+git20261103.da5291b: Source0 is triton-lang/triton commit 5889527, Source1 is triton-riscv tag nightly/20260913-da5291b; the two patches handle system build tools (cmake/ninja/nanobind) and tool discovery under /usr/lib64/buddy-mlir/llvm/bin respectively; Requires: buddy-mlir, buddy-mlir-llvm, clang.
  • python-tilelang-ruyiai 0+git20261028.0b7d66e: the main source anchors tilelang-riscv commit 0b7d66eb (commit message “[RISC-V] Add TileKernels runtime tests and refresh docs (#3)”), and packages five submodules separately: TileLang/tvm 882a7748, dmlc-core 3031e4a6, rang cabe04d6, tvm-ffi ae346ec9, DLPack 93c8f2a3; the five patches handle the tvm-ffi version ceiling, torch-c-dlpack-ext and patchelf, buddy-mlir toolchain discovery, the z3 soname, and the libbacktrace switch; BuildRequires: python3dist(torch), runtime dependencies buddy-mlir-llvm and clang.

All three specs share the same LLVM/MLIR chain: buddy-mlir carries its own pinned LLVM build, while triton and tilelang depend on the buddy-mlir-llvm package. This structure dictates the upgrade order—buddy-mlir first, then the two Python packages; changing the anchor at any layer requires a synchronized rebuild.

2.2 Version anchors: triton stuck at the 09-13 nightly, tilelang at 10-28, buddy at 0.1.2 (11-03)

Date: 2026-11-03　Source: triton-riscv nightly 2026-09-13, tilelang-riscv commit 0b7d66e, buddy-mlir 0.1.3, buddy-mlir 0.1.4.dev20261103

The version numbers of the trio all look recent, but their code anchors differ, and each is worth checking line by line:

  • The triton package version string is 3.8.0+git20261103.da5291b, where 20261103 is the packaging date; the actual triton-riscv code comes from the 09-13 nightly/20260913-da5291b tag (release record 09-14 01:41 UTC), roughly 50 days after merge. The commit message for that tag is still updating buddy-mlir to nightly/v0.0.9.dev..., showing how old the anchor is.
  • The tilelang package anchors 0b7d66eb, corresponding to PR #3 “Add TileKernels runtime tests and refresh docs”, with the version string written as 0+git20261028. This means PR #5 (TileOps streaming load and quantization paths), merged on 11-03, is not in this packaging source snapshot—the snapshot lags the repository by this period’s most important feature.
  • The buddy-mlir package says 0.1.2, with source 60f354a7; upstream’s official release is already at 0.1.3 (released 10-31 23:01 UTC, 11-01 07:01 Beijing time), and the nightly is at 0.1.4.dev20261103. The spec is one patch release behind.

Version strings carrying the packaging date make it easy to read “3.8.0+git20261103” as 11-03 code; the actual code date must be traced back to the Source1 tag or commit. Once a package is built and released, there is a fixed delay between its capabilities and the repository HEAD, and that delay needs to be shortened by subsequent bump commits.

2.3 openRuyi clears its books the same day: seven PRs merged, packaging fills the whole day (11-03)

Date: 2026-11-03　Source: openRuyi commit list, PR #1559 firecracker, PR #1563 Node.js, PR #1570 patch, PR #1534 simdjson, PR #1564 debuginfo

The main repo saw twenty commits and seven PR merges in the window, filling nearly the entire day: 10:03 merged #1570 (patch bumped to 2.8.1, with security-fixes); 14:12 merged #1563 (Node.js 26.13.0, switched to system libraries); 15:22 merged #1559 (added firecracker); 15:59 merged #1350 (the RuyiAI trio); 16:40 merged #1534 (simdjson 5.0.8, running upstream tests offline); 16:54 merged #1564 (added debuginfo to the linux package, gating CONFIG_DEBUG_INFO_SPLIT); 20:16 merged #1575 (fixed the buddy-mlir source URL).

The composition of the twenty commits matches: 3 for the RuyiAI trio, 1 for the buddy-mlir source URL fix, 2 for simdjson, 2 for the linux build, and the remaining 12 for Rust dependency fill-ins (sval series, phf 0.9, value-bag, slog, no-panic, serde-fmt, etc.), pushed together at 15:22. The thirteen-commit Prometheus dependency batch is not in this period’s merge list; that batch remains in the open queue.

2.4 ruyi main repo: zero commits, zero new tags; 0.54.0-beta.20261102 remains the only pre-release (11-03 status)

Date: 2026-11-03 (status)　Source: ruyi commit list, Release 0.54.0-beta.20261102, PyPI ruyi

The ruyi main repo had zero commits and zero new tags in the window. The latest Release is still 11-02’s 0.54.0-beta.20261102; 0.54.0b20261102 on PyPI was uploaded at 11-02 18:37 (Beijing time), and the stable channel remains 0.53.0.

The changes recorded last period—ABI host compatibility, package-fetch error reporting, and others—have landed with this beta; there are no follow-up fixes or a second beta this period. What’s worth watching next is whether 0.54.0 gets an RC before going stable, or wraps up directly with this beta.

2.5 openRuyi 2026.10 still missing; no November content on the news page (11-04 status)

Date: 2026-11-04 (status)　Source: openRuyi news page, openRuyi 2026.09 release announcement, Releases

The October 2026 monthly release announcement has still not appeared; the latest release announcement on the news page is still 2026.09 from 09-30, and November has no new content either. Following the cadence of 6-30, 7-23, 8-27, 9-30, the October edition is now a full month absent.

The experimental tags for 2026.05 through 2026.09 on the Releases page were backfilled all at once on 10-19 and cannot be counted as an October release. October’s news page has only two feature articles (ecosystem infrastructure and Ruyi Firmware), both published on 10-30.

III. Vector Extensions and Operator Optimization (VecIntrinBench / IntrinTrans / FBGEMM)

3.1 The three vector repos remain silent; latest commits still stuck at 02-13, 06-25, 07-13 (11-04 status)

Date: 2026-11-04 (status)　Source: VecIntrinBench, IntrinTrans, FBGEMM

None of the three “vector”-themed repos had any in-window commits this period; their latest commit dates are VecIntrinBench 02-13, IntrinTrans 06-25, and FBGEMM 07-13. The three originally formed a triangle of “what to measure, how to translate, how to implement operators,” and now they have been stalled for nearly nine months, four months, and three months respectively.

The differing stall points indicate this is not a single unified project termination but rather each cooling down naturally on its own. VecIntrinBench has been stalled the longest, which most directly affects coverage assessment: with the benchmark not updated, the set of intrinsics it tests will drift further and further from the set the compiler actually supports, while the LLVM-side A100/AME lowering chain continues to expand (see 1.3).

3.2 Operator work shifts to tilelang-riscv: 21 files, test surface extended to streaming load and INT8/FP8 quantization (11-03)

Date: 2026-11-03　Source: PR #5, test file list, PR #4

Among the 21 files in PR #5, tests and documentation account for the bulk, which distinguishes it from a purely functional PR. The three newly added tests cover byte fidelity of streaming load, IEEE arithmetic regression, and INT8 quantization respectively; four existing tests realign the numerical paths of existing operators:

  • test_fp8_quant_per_block.py
  • test_int8_dequant.py
  • test_paged_kv_cache_write.py
  • test_elementwise_activations.py

operator_inventory.py also saw additions and deletions (+9/−14), indicating the operator inventory itself is being adjusted.

On the documentation side, BuildOnSG2044.md adds 90 lines and removes 34, with SG2044 remaining the reference platform; tilelang/tladapter/toolchain.py removes machine-specific paths in favor of discovery from the distribution layout. This aligns with the openRuyi packaging patch merged the same day: both the source tree and the distribution are shifting from “assembling paths from environment variables” to “standard layout discovery.”

What remains uncovered is RVV masking and max reduction: PR #4 has been unmerged since 09-28, and the currently merged PR #5 does not touch this path either.

IV. Buddy Compiler Updates

4.1 buddy-mlir resumes commits; nightly 0.1.4.dev20261103 re-released (11-03)

Date: 2026-11-03　Source: commit list, PR #1017, PR #1020, nightly dev20261103

Two commits landed on the main branch during the window. 59c29fc7 at 13:07 (PR #1017 “Fix narrowing in scalable VIR piece counts”) modifies VIRSetVLLowering in the VIR-to-vector conversion pass (VIRToVectorPass.cpp, under midend/lib/Conversion/VIRToVector/): when computing the number of VL segments for RVV scalable vectors, it explicitly casts the return value of llvm::divideCeil to int64_t to avoid narrowing. PR #1020 at 21:49 only updates the torch version constraint in requirements.txt, which is build infrastructure.

At 18:23, nightly 0.1.4.dev20261103 was re-released, three days after the previous dev20261030. The observation in the previous briefing that “the main branch stalled after 0.1.3 was cut” is broken this period, but only one of the two commits touches RVV lowering, so the change surface is small.

4.2 Distro spec pins 0.1.2, one patch behind the official 0.1.3 (11-03)

Date: 2026-11-03　Source: buddy-mlir.spec, 0.1.3 release, triton-riscv PR #91

openRuyi’s spec says 0.1.2, with the source anchored at 60f354a7; upstream’s official release is already at 0.1.3 (10-31 23:01 UTC), and the nightly is at 0.1.4.dev20261103. The downstream triton-riscv dependency anchor also remains at dev20261030 (#91 merged on 10-31) and has not moved to the official 0.1.3.

Neither downstream has caught up with the same release: the distro is one patch version behind, and triton-riscv is one nightly tag behind. The content difference is minor (0.1.3 was cut from the 10-29 main branch head), but reproducibility differs—nightly tags age out under build retention policies, while official release tags do not.

V. Community, Events, and Official Homepage

5.1 Official homepage’s three pages unchanged; two blog posts, twenty-three documentation chapters (11-04 status)

Date: 2026-11-04 (status)　Source: RuyiAI official homepage, blog index, documentation index

The sha256 of the three pages index.html, blog.html, and docs.html match the previous issue; all unchanged. The homepage indexes 3 items, the blog has 2 posts (“Triton’s RISC-V Adaptation” and “PyTorch RISC-V CI in Practice”), and the documentation has 23 chapters. The official homepage added no new content in this window, in contrast with the version activity on the ruyi side.

5.2 Forum adds ruyi script installation guide; biweekly progress 080 still not out (11-03)

Date: 2026-11-03　Source: RuyiSDK developer community, script installation and upgrade guide, biweekly progress issue 079

At 17:50, the forum added #2902 “Instructions and Usage Guide for Installing and Upgrading ruyi via Script,” covering two scenarios: upgrade when ruyi is already installed locally, and a fresh install when it is not. The script installs to ~/.local/bin and requires no administrator privileges. The post explicitly states that the binary version the script currently pulls is 0.52.0—one version behind the stable release 0.53.0 and two levels behind 0.54.0-beta.

In the same period there was also #2901 “How to Install and Upgrade ruyi via Script,” which has been deleted by its author. The most recent biweekly progress issue is still 079 from 10-26; issue 080 has not been released. On the two-week cadence, the next issue falls around 11-09.

5.3 ruyiai-daily 11-03 issue archived (11-03)

Date: 2026-11-03　Source: ruyiai-daily, 11-03 issue text

The daily intelligence repository committed daily-news: 2026-11-03 at 06:24 (Beijing time) on 11-03, continuing its fixed cadence between 22:20 and 22:40 (UTC) each day. This issue covers ABI probing in ruyi 0.54.0-beta and upstream TileLang (tile-ai organization) PRs such as Ascend FlashMLA; the only addition directly related to the RuyiAI stack is the ruyi beta item, already recorded in the previous daily report, so this issue does not break it out again.

5.4 Six groups of external news queries yield no in-window hits; no relevant arXiv papers in window (11-04 status)

Date: 2026-11-04 (status)　Source: Google News RSS, arXiv

Five groups of Chinese and English queries—RuyiAI, RuyiSDK, openRuyi, RuyiSDK RISC-V, and RuyiAI when:3d—returned zero hits in the window. “如意 RISC-V” returned 8 items, but the latest is a 10-25 summit side note and the rest are old news from March to October, none within the window. Although there were general RISC-V news items that day (OpenBSD 8.0 expanding RISC-V support, RISC-V memory copy selection in Linux 7.4, etc.), they are not directly related to this topic and are excluded per the established criteria.

The latest RISC-V-related arXiv paper stops at 10-31 (sGEMM performance analysis of ET-SoC-1); there are no new papers on AI compilers or vector optimization within the window.

VI. Trend Observations

6.1 From source builds to distro packages: the RuyiAI stack’s distribution path closes the last mile

After the specs for the three-piece set entered openRuyi, the RuyiAI stack’s distribution path was written into distro configuration for the first time: previously it was “pull source + set environment variables + build LLVM yourself”; now the packaging repo contains an RPM dependency chain, with buddy-mlir providing the LLVM/MLIR prefix and triton and tilelang depending on buddy-mlir-llvm. Once the build artifacts enter the repository, the installation barrier for users drops from “can build a compiler” to “can install a package”; for the project, versions and dependencies are written into auditable specs for the first time.

This is also where the value of the seven-week review lies: what is being contested is not features but distro rules—path discovery, dependency ceilings, build isolation, package names, and Provides. PR #1575 fixed the source address that same day, showing that this chain is still fragile, but it can already run through the merge process.

6.2 Packaging anchors lag upstream: the date in the version string is not the code date

Among the three specs, triton’s code stops at 09-13, tilelang at 10-28, and buddy at 0.1.2; yet all three repositories still had new activity on 11-03. The most striking is tilelang: PR #5, merged on 11-03, was the first feature after eighteen days of silence, but it is not in the RPM merged that day—the package is anchored to 0b7d66eb from 10-28.

The version string 3.8.0+git20261103 reinforces misreading, treating the packaging date as the code date. For distro users, this means “you installed some snapshot,” not “you installed the latest.” Going forward, either establish a regular bump process or state the snapshot date clearly in the package description; otherwise, with every merged feature, the gap between the package and the repository widens a little more.

6.3 Two development lines resume the same day; ruyi mainline and openRuyi releases remain static

On 11-03, tilelang-riscv ended eighteen days of silence, buddy-mlir resumed nightly builds, and openRuyi merged seven PRs in one day; development-side activity concentrated on compiler backends and packaging. On the other side, the ruyi main repository had zero commits and zero new tags, and openRuyi’s 2026.10 monthly release is still missing.

The two lines are not in sync: code moves, releases do not. The previous issue summarized this state as “the bottleneck is in releases, not development,” which still holds this issue. The next observation points are whether the openRuyi November release includes the three-piece set, and whether triton-riscv’s #92 rebase is merged—the former determines whether the distro can ship, the latter determines where the next bump of the triton package lands.

Appendix

Source Verification Table

Source Verification Result
RuyiAI-Stack org (key repos) pytorch: zero commits in the riscv branch window; head commit 81ecd427 is a whole-branch replay at 11-03 03:00; the twenty upstream commits on main are unrelated to this stack; llvm-project: one CI workflow change in the riscv branch (bef335e2); no additions to the A100/AME pipeline; triton-riscv: zero commits, sixteen open PRs; tilelang-riscv: two commits (PR #5 merged); VecIntrinBench, IntrinTrans, FBGEMM, harness, cpuinfo, torq-tile, pytorch-ci, dsh-osc have no in-window commits; remaining repos not expanded one by one
ruyisdk org (key repos) ruyi: zero commits, zero new tags; latest Release remains 0.54.0-beta.20261102; packages-index: zero commits; remaining repos not expanded one by one
openRuyi-Project org Main repo: twenty commits, seven PRs merged (#1570, #1563, #1559, #1350, #1534, #1564, #1575); new SPECS: buddy-mlir, python-triton-ruyiai, python-tilelang-ruyiai; lookout: two commits (dependency and rate-limit fixes); TakoPack and kvm-unit-tests have pushes but no in-window commits on the default branch
buddy-compiler/buddy-mlir Two commits (#1017, #1020) plus nightly 0.1.4.dev20261103, three days after the previous nightly; stable release remains 0.1.3 (10-31 23:01 UTC)
ruyi package manager / PyPI No new commits or tags in the window; latest PyPI 0.54.0b20261102 (11-02 18:37 Beijing time); stable release 0.53.0
openRuyi distro news page No November content; the 2026.10 monthly release announcement is still missing; latest release announcement is 2026.09 on 09-30; the two October features went live on 10-30
RuyiSDK developer community forum New #2902 script installation guide (11-03 17:50); #2901 deleted by its author; biweekly progress 080 not yet published, most recent is issue 079 on 10-26
Official homepage (ruyiai.org) Three pages unchanged: homepage index 3 items, blog 2 posts, docs 23 chapters; sha256 matches the previous issue
ruyiai-daily 11-03 issue archived (11-03 06:24 Beijing time); content does not conflict with this issue’s framing
Google News RSS (six groups, Chinese and English) RuyiAI, RuyiSDK, openRuyi, RuyiSDK RISC-V, RuyiAI when:3d: zero hits; the 8 “如意 RISC-V” items are all old news outside the window and were not included
arXiv Latest RISC-V-related papers stop at 10-31; no new papers on AI compilers or vector optimization in the window

Full Source List