Research window: 2026-10-27 04:30 ~ 2026-10-28 04:30 (Beijing time, past 24 hours), contiguous with the previous issue (cutoff at 10-27 04:30).

Sources: Full-repository review of GitHub organizations (RuyiAI-Stack, ruyisdk, openRuyi-Project, buddy-compiler, checking commits, PRs, and Releases within the window repo by repo; upstream forks filtered by keywords such as RISC-V / RVV / XuanTie, with irrelevant upstream commits excluded), openRuyi commit and PR merge statistics, ruyi package manager Releases, RuyiSDK developer community forum, ruyiai-daily daily intelligence archive, three-page snapshot of the official RuyiAI homepage, arXiv search, Google News RSS targeted Chinese and English queries (via proxy).

This Issue’s Index

  • Today’s Highlights: The three-piece suite enters distro packaging, triton-riscv swaps anchors, VIR adds Python bindings (10-27)
  • I. RuyiAI Stack Progress (PyTorch / Triton / TileLang RISC-V adaptation)
    • 1.1 llvm-project: riscv branch rebased for the fifth time in six days, baseline moves forward another 237 commits (10-27)
    • 1.2 pytorch: riscv branch silent for the sixth day, twenty commits on main branch still upstream (10-27 status)
    • 1.3 triton-riscv: buddy-mlir anchor jumps straight from 10-17 to 10-27, skipping two levels (10-27)
    • 1.4 tilelang-riscv: main branch silent for the twelfth day (10-27 status)
  • II. RuyiSDK Toolchain and Distro
    • 2.1 openRuyi PR #1350: RuyiAI three-piece suite enters the distro, author responds to review comments item by item same day (10-27)
    • 2.2 openRuyi PR #1352: PyTorch RISC-V adaptation packaged separately, ships with smoke test after install (10-27 status)
    • 2.3 openRuyi: 45 commits, 12 PRs merged, Samba family bumped to 4.25.1 with Waf build in one pass (10-27)
    • 2.4 openRuyi: three reverts withdraw the “ship LLVM IR with packages” approach (10-27)
    • 2.5 Review queue: qemu 11.1.2, qemu-rustsbi, libvirt, and cross toolchain (10-27 status)
  • III. Vector Extensions, Architecture Testing, and Operator Optimization
    • 3.1 Support matrix adds SpacemiT K3 Pico-ITX Bianbu 4.0.8 report, rated good (10-27)
    • 3.2 Support matrix adds VisionFive 2 Lite Ubuntu 24.04.5 report, rated basic only (10-27)
    • 3.3 Vector repos and FBGEMM all silent, no new arXiv entries in window (10-27 status)
  • IV. Buddy Compiler Updates
    • 4.1 VIR adds Python bindings: from buddy-opt-only to a programmable dialect (10-27)
    • 4.2 Five under review: piece count to int64, Whisper preprocessing reuse, buddy-server source cleanup (10-27)
    • 4.3 Nightly dev20261027 released, downstream anchors connected same night (10-27)
  • V. Community, Events, and Official Site
    • 5.1 Official site’s three pages unchanged, two blog posts, twenty-three doc chapters (10-27 status)
    • 5.2 No new forum posts, latest still the 10-22 summit recap and course notes (10-27 status)
    • 5.3 ruyiai-daily one issue, harness plugin split, ruyi-imager selection dialog fix (10-27)
    • 5.4 Zero external news hits, neither openRuyi 2026.10 nor ruyi 0.54.0 released (10-27 status)
  • VI. Trend Observations
    • 6.1 Expression layer, tool layer, and distribution layer each gain a piece on the same day
    • 6.2 Beyond pre-release cleanup, the distro starts doing subtraction

Today’s Highlights: Trio Enters Distro Packaging, triton-riscv Re-anchors, VIR Gains Python Bindings (10-27)

Date: 2026-10-27　Sources: openRuyi PR #1350, triton-riscv PR #90, buddy-mlir PR #1009

This issue’s three main threads each advanced one step within the same window — and connected with each other for the first time.

The first is the distribution layer. openRuyi’s PR #1350 “Add Ruyiai packages” submits three specs at once — buddy-mlir, python-triton-ruyiai, and python-tilelang-ruyiai (3 commits, 9 files, +666/−0). Opened on 9-21, it drew change requests from maintainer Z572 on 9-24, with discussion stalling on 9-28; on 10-27 between 17:55 and 18:54 (Beijing time), author nekorouter replied to three review comments in succession, addressing point by point the git build dependencies, whether buddy-mlir’s bundled LLVM should be externalized, and the cost of switching to a GCC build. The same day, another PR #1352 packaged PyTorch’s RISC-V adaptation separately. Neither has been merged, but both have moved from “shelved” back to “converging item by item.”

The second is the tooling layer. At 19:43, the renovate bot submitted and merged triton-riscv’s dependency anchor bump (#90, +2/−2): buddy-mlir jumps straight from nightly/v0.1.1.dev20261017 to nightly/v0.1.3.dev20261027, skipping the entire 0.1.2 release and two nightly builds. The previous daily listed “whether the anchor will be updated” as an item to watch; this issue delivers the answer: it was updated, and two levels at once. This means the seven VIR scalable-vector changes from the night of 10-26 now enter the downstream build chain as of this issue.

The third is the expression layer. buddy-mlir’s #1009 “[midend][VIR] Python bindings” merged at 22:42 (12 files, +614/−1), turning VIR — a dialect previously runnable only inside buddy-opt, where operators had to be assembled by hand with ir.Operation.create("vir....") and types by hand with ir.Type.parse("!vir.vec<...>") — into a proper buddy_mlir.dialects.vir module, following the standard path of ODS plus C API plus nanobind extensions.

Taken together: VIR can express scalable vectors (previous issue), can now be driven from Python (this issue), and below that sits a distro packaging channel (under review this issue). What this stack has always lacked is not any single capability but the connection of its three segments — expression, tooling, distribution — and this issue is a rare day on which each made progress.

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

1.1 llvm-project: riscv branch rebased for the fifth time in six days, baseline advances another 237 commits (10-27)

Date: 2026-10-27　Sources: riscv branch commit list, new head ed439f3e, comparison with previous head

The riscv branch completed its fifth full-branch rewrite at 23:00 Beijing time on 10-27, with the head moving from a18a0434 to ed439f3e; the title remains “[RISCV] Add A100 HP/SP and pack/unpack lowering with calibrated scheduling (#31)”. The comparison with the previous head is diverged: 237 commits ahead, 26 behind, 300 files differing. The 26 commits behind are exactly the local patch set, matching the 10-26 record precisely.

The 20 local commits were rewritten and force-pushed within the same minute (committer timestamps clustered between 15:00:29 and 15:00:31), while author dates run from July 1 through October 3: the newest is this round’s head #31, the A100 HP/SP and pack/unpack lowering (authored 10-03), and the oldest is #9b72a085, a CI trigger fix (authored 7-01). Unchanged author dates with uniform committer timestamps are the hallmark of a full-branch replay, indicating no new local functionality this round—only the existing patch set moved onto a new baseline.

The rebase sequence now stands at 1769 commits on 10-21, 275 on 10-23, 474 on 10-25, 221 on 10-26, and 237 on 10-27. Five rebases in five days, at a steady one-per-day cadence. Last issue’s assessment—that this branch’s day-to-day activity has fully become baseline tracking—is confirmed for a second time; the only source of local feature increments remains upstream, or must await new patches from the BOSC AME and Buckyball side.

1.2 pytorch: riscv branch silent for a sixth day, the twenty main-branch commits remain upstream (10-27 status)

Date: 2026-10-27 (status)　Sources: pytorch riscv branch, pytorch main branch

The riscv branch head is still Add riscv64 image locally (#51) from 10-22 03:00 Beijing time, with zero commits from 10-22 through 10-27—a sixth consecutive day. The three-day and five-day silences recorded in previous issues now extend to six days; the two mainline RVV capability proposals (#46, vector extension support for ATen, and #48, RISC-V Vector CPU capability) saw no updates this issue either.

The main branch saw 20 commits over the same period, all upstream syncs, none RISC-V-related: five fill in C++ meta kernels (ne.Scalar, eq.Tensor, le.Scalar, le.Tensor, bitwise_and.Tensor), one has ROCm Inductor skip the CK forward convolution template (conv_transpose), and the rest fall under build and test infrastructure. This matches last issue’s conclusion: upstream tracking and RISC-V replay on this branch are two pipelines on different cadences—the former updates daily, the latter is replayed manually at chosen intervals.

Worth reading alongside is the distribution side—on the same day, openRuyi PR #1352 is packaging this branch’s artifacts into the python-torch-ruyiai package (see 2.2). The branch itself is static, but its downstream distribution path is moving, and that is the only new information on the pytorch front this issue.

1.3 triton-riscv: buddy-mlir anchor jumps from 10-17 straight to 10-27, skipping two levels (10-27)

Date: 2026-10-27　Sources: triton-riscv PR #90, commit 4a066f1f, buddy-mlir nightly release list

At 19:43, #90, submitted by the renovate bot, was merged; the change is just two lines (+2/−2): buddy-compiler/buddy-mlir goes from nightly/v0.1.1.dev20261017 to nightly/v0.1.3.dev20261027. This is not a routine minor-version follow but a catch-up across levels—it skips the 0.1.2 formal release (10-25 06:18) and two nightly builds on the 0.1.3 line (10-26 06:37, 10-27 08:26).

Last issue’s report listed “whether the anchor is updated and rebuilt” as an item to watch; it has now landed. The implication is concrete: the seven VIR scalable-vector changes from the night of 10-26 (#1002 through #1008) previously existed only in buddy-mlir’s source tree, while downstream triton-riscv builds still used the old 10-17 package; with the anchor switched, this batch of changes enters Triton’s operator generation pipeline.

Note that updating the anchor only resolves “can it be used,” not “it has been used.” Apart from this dependency update, the triton-riscv main branch saw no other commits in this window, nor any corresponding adaptation code changes; whether buddy-mlir introduced interface changes between 0.1.1 and 0.1.3 that affect Triton calls can only be confirmed after an actual downstream rebuild and passing tests.

1.4 tilelang-riscv: main branch silent for a twelfth day (10-27 status)

Date: 2026-10-27 (status)　Sources: tilelang-riscv commit list, open PR list

The last commit on the tilelang-riscv main branch is still from 10-16 10:52, marking a twelfth consecutive day without commits; open PR #4 has been stalled since 09-28. In contrast with triton-riscv’s anchor switch, this side has not even seen a dependency update.

The distribution side, however, has given it a new position: openRuyi PR #1350 includes a python-tilelang-ruyiai spec covering 4 patches (relax Apache TVM FFI 0.1.10, switch to system build dependencies, discover the buddy-mlir toolchain, skip the z3 soname rewrite). In other words, the repository itself is stalled, but the path to “available as a distro package” is advancing—the only substantive action related to tilelang-riscv this issue.

II. RuyiSDK Toolchain and Distributions

2.1 openRuyi PR #1350: The RuyiAI trio enters the distribution; author responds to review comments item by item the same day (10-27)

Date: 2026-10-27　Source: PR #1350, PR #1350 review comments, PR #1350 commits

PR #1350 is the most important item in the distribution layer this issue: a single PR adds three packages at once—buddy-mlir (an LLVM-based MLIR compilation framework), python-triton-ruyiai (RISC-V Triton), and python-tilelang-ruyiai (RISC-V TileLang backend). All 3 commits landed on 9-21 between 09:46 and 09:48 (within two minutes), totaling 9 files, +666/−0.

The timeline is worth recording: the PR was opened on 9-21; on 9-24 maintainer Z572 raised three change requests (why git is needed, whether buddy-mlir should provide a macro file for Triton to locate its LLVM, and whether buddy-mlir should first build a fixed-version clang with GCC and then build itself with the new clang); on 9-28 the author replied and fixed two of them; then it stalled for nearly a month, until three consecutive replies at 17:55, 17:57, and 18:54 on 10-27 addressed the remaining disputes one by one.

The technical content of the three replies is more informative than the progress itself. First, triton upstream’s setup.py forcibly checks whether git can be executed, so either add git as a build dependency or modify setup.py (requiring a new patch file, which easily falls out of sync when triton updates)—the author chose the former. Second, the LLVM bundled with buddy-mlir is used only inside that package, and these packages are always pinned to a specific LLVM commit, so the author prefers to keep it inside the build process rather than externalizing it as a standalone macro package. Third, switching to GCC to build a fixed-version LLVM/clang is technically feasible, but would increase build time by at least 1.5x.

These three points all point to the same trade-off: the build chains of these RuyiAI packages are highly coupled (Triton depends on buddy-mlir’s LLVM, TileLang depends on the buddy-mlir toolchain), and once they are split apart according to the distribution’s convention of “externalizing dependencies and reusing system packages,” both build cost and mismatch risk rise. The author chose to preserve the coupling and accept the size and build-time cost—a clear statement of position on the packaging route.

2.2 openRuyi PR #1352: PyTorch RISC-V port packaged separately, with a built-in smoke test after installation (status 10-27)

Date: 2026-10-27 (status)　Source: PR #1352, python-torch-ruyiai spec file

PR #1352 packages RuyiAI-Stack/pytorch separately as python-torch-ruyiai (8 files, +783/−0). Updated the same day as #1350, it remains open, with its only commit stalled at 9-21 11:22.

The patch set reads like a complete distribution adaptation checklist: 2001 forces OpenBLAS to use cblas complex dot products, 2003 switches to system fmt, 2005 switches to system cmake dependencies, 2006 skips a useless submodule pre-build check, 2011 gates RVV kernels by target vector capability, and 2012 embeds scikit-build-core. There is also a pytorch-smoke-test.py, indicating that this package must pass a smoke test after installation—for a distribution, that goes a step beyond merely “it installs.”

The 2011 item deserves particular attention: changing the RVV kernel enablement condition from “assumed supported at compile time” to “gated by target vector capability” addresses a problem that keeps recurring in the community—on targets such as RVA20 that lack the vector extension, failing to gate at packaging time produces code that cannot run. Such fixes usually wait until users hit them on real boards; here they have entered the packaging patches in advance.

Like #1350, this package also declares AI assistance (Assisted-by: Deepseek V4.1 Flash) and follows openRuyi’s AI contribution policy with the appropriate checkboxes and attribution.

2.3 openRuyi: 45 commits, 12 PRs merged; the entire Samba family moved to 4.25.1 with Waf builds in one go (10-27)

Date: 2026-10-27　Source: openRuyi commit list, PR #1428 Samba and libraries, PR #1506 security updates, PR #1508 ceph backport

The main repo saw 45 commits and 12 PRs merged in the window, with authors distributed as Li Guan 12, Jingwiw 9, Kimmy 9, cl2t 5, misaka00251 4, Zheng Junjie 3, Sun Yuechi 1, Xiang’ao Liu 1, Hangfan Li 1. In time they fall into three batches: 17 around 15:00, 12 around 16:00, and 9 at 01:31 the next day, with the remaining 7 scattered between 12:32 and 17:36.

The largest is #1428, pushing 9 commits at once: samba upgraded to 4.25.1, tevent 0.17.2, tdb 1.4.15, talloc 2.5.0, cmocka 2.0.2, and jack2 and rpm-config-openruyi both switched to the Waf build macro. This is not a scattered upgrade but an alignment of the entire Samba family (including its dependency libraries) at a single point in time; every package depending on the tevent/tdb/talloc ABI must be rebuilt accordingly—a classic “coordinated upgrade” in a distribution.

The security line is handled by #1506, carrying 12 packages at once: sysrepo 5.2.27, libzip 1.12.1, libyang 6.4.13, libical 4.0.7, vim 9.2.1201, squashfuse 0.6.5, simdutf 9.3.2, pcre2 10.49, libheif 1.23.6, imagemagick 7.1.2.34, cups 2.4.20, and cpp-httplib 0.63.0, all titled with the [security-fixes] tag. There is also a ceph backport (#1508, ceph-volume partition db/wal fix, plus fixes for mgr, cephfs-mirror, and rgw).

13 new packages were added, mostly in the Go ecosystem: the go-git v6 family of three (go-git, fixtures, billy), goldmark-highlighting-v2, go-udev, go-evdev, gonetworkmanager-v2, jaypipes/ghw, mozillazg/go-pinyin, kustomize, go-k8s-kube-proxy, go-k8s-cluster-bootstrap, and aws-lc-sys 0.46; gcfg was renamed to gcfg-v2 in place. These additions and dms-shell’s replacement of its embedded vendor bundle with packaged Go dependencies (#1511) are two sides of the same thing—moving Go projects from “bundling their own vendor directory” to “using system packages,” which facilitates unified upgrades and CVE response going forward.

Other merges: rust-aws-lc-rs upgraded to 1.18.2 with aws-lc-sys 0.46 added (#1518), docker-cli 29.9.2 (#1515), systemd taking over /etc/modules-load.d (#1510),
python-opentelemetry-semantic-conventions 0.65b0 (#1517), and SQL-migrate and kubecomps dependency completions (#1365, #1356, #1358).

2.4 openRuyi: three reverts withdraw the “ship LLVM IR with packages” approach (10-27)

Date: 2026-10-27　Source: PR #1509 Revert llvm ir, openRuyi commit list

#1509, merged at 15:15, has only three commits and a net deletion of 105 lines (+5/−105), reverting three experimental packaging changes previously made in the same repository: the llvmir feature of gsl, pixman being built with clang and shipping IR files, and libjpeg-turbo shipping LLVM IR files.

The PR description gives no reason; from the commit contents, the direction was to compile libraries to LLVM IR and ship it with packages, leaving an interface for later re-optimization or deferred code generation. The withdrawal of the entire line indicates this approach was judged “not to be kept for now” before release. For a RISC-V distribution this is an interesting trade-off: IR distribution could in theory reuse upstream optimizations, but it brings a chain of issues around package size, ABI, and debug symbol consistency, and requires infrastructure-side coordination, making short-term benefits hard to realize.

This also marks a divergence between this issue’s openRuyi and previous ones: the keyword in past issues was “add”—adding packages, adding security fixes, adding Rust crates; this issue, besides additions, also features explicit subtraction.

2.5 Review queue: qemu 11.1.2, qemu-rustsbi, libvirt, and cross toolchain (status 10-27)

Date: 2026-10-27 (status)　Source: openRuyi open PRs, PR #1520 qemu 11.1.2, PR #1516 qemu-rustsbi, PR #1490 cross toolchain

There are 10 open PRs updated within the window; apart from the two RuyiAI-related ones, the rest fall into three categories by direction.

Virtualization and firmware: #1520 upgrades qemu to 11.1.2, #1519 gives libvirt ownership of
/var/lib/libvirt/secrets and fixes rbd storage pools on Ceph 21, #1516 adds qemu-rustsbi (an SBI implementation written in Rust, submitted by luojia65), and #1436 adds fwupd support to ovmf.

Toolchain and base libraries: #1490 remains WIP, aiming to add a cross toolchain targeting riscv64; #1429 fixes krb5’s build configuration and package defaults; #1521 addresses build failures in several python packages.

System management: #1367 adds SQL-migrate.

What these have in common is “paving the way for the next release”: the qemu major-version upgrade and the cross toolchain are both heavy pre-release actions that typically do not complete within the window, so the pace of progress in subsequent issues will determine whether the 2026.10 release can stay on schedule.

III. Vector Extensions, Architecture Testing, and Operator Optimization

3.1 Support matrix adds SpacemiT K3 Pico-ITX Bianbu 4.0.8 report, rated good (10-27)

Date: 2026-10-27　Source: support-matrix commit db59e82c, K3 Pico-ITX directory

The 12:35 commit creates a board directory for the SpacemiT K3 Pico-ITX and adds a Bianbu test report: 367 lines in English, 359 in Chinese, with a CPU information screenshot and board-level notes in both languages. Report metadata is sys: bianbu, sys_ver: 4.0.8, sys_var: LXQt, status: good, last_update: 2026-10-16.

The good rating is a relatively high tier in the support matrix, indicating that the desktop (the LXQt variant in this case) is functionally complete in testing with no blocking issues. K3 is SpacemiT’s new-generation product line; previously the matrix mostly covered K1 and other K3 form factors. This is the first entry for the Pico-ITX form factor, giving developers who obtain the small board a usable starting document.

3.2 Support matrix adds VisionFive 2 Lite Ubuntu 24.04.5 report, rated only basic (10-27)

Date: 2026-10-27　Source: support-matrix commit 92143f8e, VisionFive2_Lite directory

The 12:38 commit adds an Ubuntu test report for the StarFive VisionFive 2 Lite (269 lines in English, 260 in Chinese), with metadata sys: ubuntu, sys_ver: "24.04.5", status: basic, last_update: 2026-10-26. The image is Canonical’s official preinstalled server build ubuntu-24.04.5-preinstalled-server-riscv64+jh7110.img.xz, flashed via the SFFB tool into fastboot, with a USB-to-TTL serial console.

Compared with the previous item, both reports were merged on the same day by the same author (zhiyao310), but the conclusions differ: the Ubuntu report is rated basic, meaning the system boots and basic functions work but with clear limitations — a “runs, but not recommended for daily use” tier. The rating gap between Bianbu and Ubuntu on the same JH7110 platform shows that the practical usability of RISC-V distributions still depends on how deeply vendors adapt their images, not on kernel support alone.

3.3 Vector repos and FBGEMM all silent, no new arXiv entries in window (10-27 status)

Date: 2026-10-27 (status)　Source: VecIntrinBench, IntrinTrans, FBGEMM, arXiv

The vector and operator repositories again saw no commits this period, and their idle times continue to lengthen: VecIntrinBench last active 02-13, IntrinTrans 06-25, cpuinfo 05-20, FBGEMM 07-13, AME-operator 09-30, torq-tile 04-09. Most of these repositories have been silent for most of the past year, indicating that vector intrinsic testing and the operator side are not current investment priorities for the RuyiAI stack.

An arXiv search filtered on RISC-V plus compiler, vector, and inference returned no new preprints in the window; the latest remain the two from 10-23 (an architectural comparison of open-ISA supercomputers, and LLM-assisted repair of RISC-V processor defects), and the closest to RVV is still the 10-21 “Reorienting the Vector Axis.” All three serve as trend references only and are not itemized as technical judgments.

IV. Buddy Compiler Updates

4.1 VIR Gains Python Bindings: From a buddy-opt-Only Tool to a Programmable Dialect (10-27)

Date: 2026-10-27　Source: PR #1009, buddy-mlir commit list

Merged at 22:42, #1009 is the core Buddy Compiler action in this window: 12 files, +614/−1, adding a new buddy_mlir.dialects.vir module. The commit message states the pain point plainly — VIR previously had no Python bindings at all, so VIR decode attention could only assemble ops via ir.Operation.create("vir....") and types via ir.Type.parse("!vir.vec<...>"), and the entire VIR lowering could only run inside the single buddy-opt executable.

The implementation follows the existing dialect pattern: ODS op definitions (VIRBinding.td) plus a C API plus a nanobind extension, structurally identical to upstream dialects in the same repo that ship their own types, such as quant. Per the PR description, it comes in three parts — Ops, Types, and pass registration that hooks VIR lowering into Python.

The significance lies not in the tooling itself but in composability: once VIR can be constructed and lowered directly from Python, op descriptions, shape inference, and test cases can all live on the Python side, and frontends (Triton, TileLang) no longer need C++-side hooks to interface with VIR. For an intermediate representation that could previously only be validated inside a single executable, this marks a shift from “compiler internal” to “externally callable dialect.”

Note that #1009 was followed immediately by #1011 “Cast the scalable VIR piece count to int64_t” (open), indicating that integer-width issues on the scalable vector path have only just been touched in the past two days. The Python bindings merely open the door; stability is still being worked out.

4.2 Five PRs Under Review: piece count to int64, Whisper Preprocessing Reuse, buddy-server Source Cleanup (10-27)

Date: 2026-10-27 (status)　Source: PR #1011, PR #1013, PR #1012, PR #1010

Five open PRs were updated during the window, falling into three groups.

VIR and scalable vectors: #1011 explicitly casts VIR’s piece count from its default width to int64_t. Piece count refers to how many segments a scalable vector is split into; participating in subsequent multiply-adds as 32-bit carries overflow risk for large shapes. This fix belongs to the same cleanup category as #1008 from the previous issue (index vector width assertion).

Model examples: #1013 reuses Whisper preprocessing within each transcription; #1012 adds validation for Whisper output and enables x64 CI tests. Both are routine example quality improvements and do not involve RISC-V.

Infrastructure: #1010 reorganizes the buddy-server source and test directory structure. Separately, #993 adds the tile.upsample_nearest op and recognition pattern, and #932 fixes row padding for C move-out in Gemmini OS blocked matrix multiplication; both were also updated within the window but contain earlier content.

4.3 Nightly dev20261027 Released, Downstream Anchor Updated the Same Night (10-27)

Date: 2026-10-27　Source: Nightly v0.1.3.dev20261027, triton-riscv PR #90

buddy-mlir released nightly 0.1.3.dev20261027 at 08:26, the second nightly build on the 0.1.3 line, two days after the stable release 0.1.2 (10-25 06:18). The release cadence is back to “stable release plus nightly updates.”

At 19:43 the same day, triton-riscv set this nightly as its new anchor (see 1.3). The 11-hour gap from release to downstream re-anchoring is the fastest handoff in recent issues — the previous issue recorded a case where the anchor still had not been switched two days after release. This objectively shortens the delay from “local change” to “downstream availability,” but note that the anchor switch is an automated renovate commit and real compatibility validation has yet to follow. The next issue should check whether triton-riscv produces tests or fix commits targeting the new anchor.

V. Community, Events, and Official Homepage

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

Date: 2026-10-27 (status)　Source: RuyiAI official homepage, Blog, Docs

The sha256 of the homepage, blog, and docs pages are identical to the previous issue: 3 homepage index entries, 2 blog posts (Triton’s RISC-V port, PyTorch RISC-V CI practices), and 23 documentation chapters. No new blog posts or chapters have been added for several consecutive windows.

The contrast with GitHub-side activity continues to widen: this issue alone saw two substantive packaging PR advances in openRuyi, yet the official content pages still show only the two September articles. External communication and engineering progress are not in sync—a fairly obvious gap in the Ruyi community at present.

5.2 No new forum posts; latest still the 10-22 summit recap and course handout (10-27 status)

Date: 2026-10-27 (status)　Source: RuyiSDK developer community, Summit recap #2893, Course handout #2894

No new posts in the community forum during the window. The latest two remain dated 10-22: the RuyiSDK recap of the 6th RISC-V China Summit (10 team members on site, two technical talks, six technical posters) and the “RISC-V Linux Practice Course 02: Sufficient C Language Basics” handout.

Biweekly Progress issue 079 (published 10-26 18:02) is the most recent formal report; on a two-week cadence, issue 080 should land in early November, so there will be no new biweekly milestone between this issue and the next.

5.3 One ruyiai-daily issue, harness splits out plugins, ruyi-imager fixes selection dialogs (10-27)

Date: 2026-10-27　Source: ruyiai-daily, harness commit 07:04, ruyi-imager PR #21

ruyiai-daily committed “daily-news: 2026-10-27” at 06:53, continuing its daily-archived intelligence updates.

harness (the agent system used for RuyiAI development) committed “Split vector retrieval and multi-agent runtime into reusable plugins” at 15:04, splitting vector retrieval and the multi-agent runtime into reusable plugins. This commit has no direct RISC-V relevance, but it is a rare piece of engineering cleanup in the RuyiAI stack, and the repository—previously stalled at 10-10—resumed commits this issue.

ruyi-imager merged #21 “Require an explicit selection in selection dialogs” (corresponding to issue #20) at 14:24: selection dialogs no longer preselect entries for the user; on open they only restore previously selected values, keep the selection empty after filtering the list or selecting a tree category, and keep the confirm button disabled until the user actually makes a selection; when filtering yields no matches, an empty-state hint is shown and confirm is disabled. This is pre-release usability polish for the installer, in the same category as the previous issue’s “double-click and keyboard confirmation.”

Other notes: ruyisdk-website’s latest commit remains the 10-23 automated API data update; wechat-articles is stalled at 10-26; the main ruyi repo has had no commits since 09-25.

5.4 Zero external news hits; neither openRuyi 2026.10 nor ruyi 0.54.0 released (10-27 status)

Date: 2026-10-27 (status)　Source: Google News RSS, openRuyi distro news page, ruyi Releases

Targeted Google News queries in Chinese and English for RuyiSDK, RuyiAI, Ruyi RISC-V, Ruyi community compiler, and openRuyi returned zero hits during the window. RISC-V-related news captured in the same window—deepin’s desktop ecosystem progress at the 6th RISC-V China Summit, Pharo 14’s RISC-V JIT, Tenstorrent’s $1.5 billion Series E funding, Microchip PIC64-HPSC aerospace computing progress, and others—is unrelated to the Ruyi community and is not included in this issue.

On the distro side, both releases remain outside the window: the latest post on the openRuyi news page is still the 2026.09 release announcement (9-30), and repository tags only go up to 2026.09-experimental; ruyi’s 0.54.0 has only the 09-18 alpha tag, with the official release, per issue 079, expected at the end of October. Following the cadence of recent months (6-30, 7-23, 8-27, 9-30), the October release will most likely land at the end of this month, overlapping the 0.54.0 time window; the next issue should verify whether this materializes.

VI. Trend Observations

6.1 Expression layer, tooling layer, and distribution layer each fill a gap on the same day

Place this issue’s three events on a single timeline: on the night of 10-26, VIR completed scalable vector expressions; on the night of 10-27, Python bindings were added; and throughout 10-27, distribution packaging was being pushed. These three stages are inherently sequential—first it can express, then it can be called, and finally it can be distributed. In previous issues, the pattern was consistently “expression layer fast, tooling and distribution layers lagging”; this issue marks the first time all three lines advanced in parallel on the same day.

However, to judge whether this stack is truly closing the loop, two known gaps remain. First, the re-anchoring of triton-riscv is automated, and adaptation verification has not yet caught up; whether the interface changes between 0.1.1 and 0.1.3 will surface downstream will only be known next issue. Second, the pytorch riscv branch has had zero commits for six consecutive days, while the distribution side is already packaging it (#1352)—the package follows a branch that is not moving, and whether it will already be behind the upstream baseline by the time the package is merged is a risk worth watching.

6.2 Beyond pre-release cleanup, the distribution begins to subtract

This issue’s two sets of openRuyi actions are different in nature: one set is addition (45 commits, 13 new packages, 12 security updates, a coordinated upgrade of the entire Samba family), and the other is subtraction (three reverts withdrawing LLVM IR from bundled distribution). What we saw in previous issues was always “pre-release cleanup”—filling dependencies, clearing CVEs, switching versions; this issue is the first time we see an explicit functional rollback.

This indicates that openRuyi’s maintenance focus is shifting from “covering more packages” to “ensuring the quality boundaries of existing packages”: experiments such as IR distribution bring cascading costs in package size, ABI, and infrastructure, and are prioritized for removal under release pressure. For the RuyiAI stack, this is a two-sided signal—the packaging channel is becoming more standardized (#1350 and #1352 are both converging item by item according to distribution conventions), but tolerance for “experimental build methods” (such as embedded LLVM or self-vendored components) will decline in tandem. The author’s insistence in #1350 on keeping buddy-mlir’s LLVM inside the package is precisely a negotiation against this direction, and the outcome is worth observing.

Source Verification Table

Source Verification Result
RuyiAI-Stack organization (all repos) llvm-project: riscv branch rebased for the fifth time on 10-27 (head a18a0434 changed to ed439f3e, ahead 237, behind 26, 300 files), with all 26 local patches unchanged item by item; pytorch: riscv branch has zero commits for the sixth consecutive day, two mainline proposals have no updates, and all 20 commits on the main branch are upstream; triton-riscv: 1 dependency update (buddy-mlir anchor raised from 10-17 to 10-27); tilelang-riscv silent for the twelfth day; ruyiai-daily one issue; harness 1 plugin split; FBGEMM, cpuinfo, VecIntrinBench, IntrinTrans, torq-tile, pytorch-ci, dsh-osc have no commits within the window
ruyisdk organization (all repos) support-matrix 2 commits (SpacemiT K3 Pico-ITX Bianbu 4.0.8 rated good, VisionFive 2 Lite Ubuntu 24.04.5 rated basic); ruyi-imager 1 commit (PR #21 explicit selection in the selection dialog); packages-index has no commits within the window (latest 10-26); wechat-articles, ruyisdk-website, ruyi, riscv-gcc have no commits within the window; ruyi has no new Release (0.53.0 maintained)
openRuyi-Project organization openRuyi main repo 45 commits (Li Guan 12, Jingwiw 9, Kimmy 9, cl2t 5, misaka00251 4, Zheng Junjie 3, the remaining 3 people 1 each) + 12 PRs merged; categories include 13 new packages, 12 security updates, 1 ceph backport, 3 reverts; 10 open PRs have updates (including two from RuyiAI); ceph-ci and go-rpm-macros have pushes but no commits on the main branch within the window; no new tags (2026.09-experimental is the latest)
buddy-compiler organization buddy-mlir 1 merge (#1009 VIR Python bindings, 12 files +614/−1) + nightly v0.1.3.dev20261027; five open PRs have updates (#1010, #1011, #1012, #1013, #993, #932); buddy-benchmark, buddy-examples, compiler-eval, FeGen, gemmini, firesim have no commits within the window
RuyiSDK Developer Community Forum No new posts; the latest two are the summit recap #2893 and course handout #2894 from 10-22; biweekly progress issue 079 (10-26) is the most recent formal report
openRuyi distribution news page No new articles; the 2026.09 release announcement (9-30) remains the latest; repository tags stop at 2026.09-experimental, and 2026.10 has not been released
ruyi package manager / PyPI 0.53.0 maintained, no new alpha or beta (0.54.0-alpha.20260918 remains the most recent version); the main branch has had no commits since 09-25
Official homepage (ruyiai.org) Three pages unchanged: homepage index 3 items, blog 2 posts, docs 23 chapters; sha256 identical to the previous issue
arXiv (RISC-V) No new additions within the window; the latest are the open ISA supercomputing comparison and LLM-assisted RISC-V defect fixing from 10-23; the long-vector FlashAttention from 10-21 remains the most relevant to RVV
Google News RSS (multiple groups in Chinese and English) Targeted queries for RuyiSDK, RuyiAI, 如意 RISC-V, 如意社区编译器, and openRuyi returned zero hits; contemporaneous RISC-V news is unrelated to the Ruyi community and was not included

Complete Source List