Research window: 2026-10-10 04:30 ~ 2026-10-12 04:30 (Beijing time, approx. 48 hours; the Monday window covers the weekend’s two days, and the small overlap with the previous issue’s catch-up window is handled on a non-duplication basis).

Sources: Full-repo review of three GitHub organizations (RuyiAI-Stack, ruyisdk, openRuyi-Project commits, pull requests, and releases, via both Atom and API channels, with every item in the window individually re-verified; upstream fork commits filtered by RISC-V keywords, with irrelevant commits excluded), ruyi package manager and PyPI version verification, ruyi-imager and VS Code extension release channels, the openRuyi distro news page, the RuyiSDK developer community forum, the RuyiAI official website, the ruyiai-daily intelligence repository, arXiv search, and multiple Chinese and English Google News RSS queries (via proxy; zero hits this window, see appendix).

Issue Index

  • Today’s Highlights: Matrix expansion and stack sync advance on three fronts—riscv-gcc Ztt lands 51 commits in a single batch, PyTorch riscv branch undergoes a full-stack rebuild (23 commits), triton-riscv #84 dependency upgrade merged
  • I. RuyiAI Stack Progress (PyTorch / Triton / TileLang RISC-V adaptation)
    • 1.1 pytorch: riscv branch completes full-stack rebuild (23 commits re-landed); 8 open PRs undergo routine baseline refresh (10-11)
    • 1.2 llvm-project: riscv branch completes another nightly replay (26 commits); two FPGA PRs refreshed and pending review (10-11)
    • 1.3 triton-riscv: #84 Buddy MLIR dependency upgrade merged; #85 remains open (10-10)
    • 1.4 harness: Triton-RISCV plugin adds MySQL persistence, Redis caching, and RabbitMQ worker (10-10)
    • 1.5 Intelligence and site infrastructure: ruyiai-daily pushes the 10-11 issue; site repo sees two routine commits (10-11 ~ 10-12)
  • II. RuyiSDK Toolchain and Distro (build, toolchain, IDE, openRuyi)
    • 2.1 riscv-gcc: ztt-dev branch lands 51 Ztt backend commits in a single batch (10-11)
    • 2.2 VS Code extension: PR #263 opened; #262 remains open (10-10)
    • 2.3 openRuyi: 5 commits including docker-cli land; lookout inspection pipeline extended (10-10 ~ 10-11)
    • 2.4 Others: ruyi and PyPI remain at 0.53.0; ruyi-imager nightly channel undergoes routine refresh (10-11)
  • III. Vector Extensions and Operator Optimization (VecIntrinBench / IntrinTrans / FBGEMM)
    • 3.1 All three repos silent; MXNet / Caffe open PRs total 18 with no updates in the window (10-11 status)
  • IV. Community and Events (biweekly report, forum)
    • 4.1 No new forum posts in the window; biweekly report remains at issue 077 (10-11 status)
    • 4.2 Zero hits for external news and arXiv; no new articles on the openRuyi news page (10-11 status)
  • V. Trend Observations
    • 5.1 Dual-track rebuild cadence: both forks each complete a full-stack rebuild in the same week
    • 5.2 Ztt line accelerates for a second consecutive batch: single-batch size 36 commits → 51 commits
    • 5.3 Dependency upgrade chain closes: #86 adaptation → #84 merge

Today’s Highlights: Matrix Extension and Stack Sync Advance on Three Fronts — Ztt Single Batch of 51 Commits, PyTorch riscv Full-Stack Rebuild (23 Commits), triton-riscv #84 Dependency Upgrade Merged

Date: 2026-10-10 ~ 2026-10-11　Sources: riscv-gcc ztt-dev commit list, head commit a326bc3, pytorch riscv branch commit list, head commit 0fc3546d, triton-riscv PR #84

The GCC backend line for the matrix extension direction took another step forward this week: contributor pz9115 pushed a single batch of 51 Ztt commits to the ztt-dev branch of riscv-gcc on the afternoon of 10-11 (13:50), the largest batch since the branch was established on 09-30 (surpassing the 36-commit batch of 10-08). Ztt is a draft instruction set for the RISC-V matrix extension direction, representing RuyiAI’s GCC toolchain effort alongside the BOSC AME / A100 line on the LLVM side. This batch performs systematic refinement of Ztt backend infrastructure: comprehensive reuse and caching of the descriptor system (TC / ACC / zip / row-column / constructors and consumer, unary operand state), indexed lookup and registration (builtin decoders, store declarations, overload candidates, profile and type lookups, datatype names and registration keys), zero-value and narrow-carrier simplification (zero registers for scalar / control inputs, narrow Ztt scalar carriers, floating-point zero-offset shift folding), descriptor propagation along branch edges and fallthrough, descriptor cleanup after DCE, factorization of dynamic workspace computation, and updates to LTO dump checks and optimized instruction checks. All 51 are newly developed commits (author and committer timestamps at the same push point), with the branch head advancing to a326bc3 “Update Ztt descriptor and LTO dump checks”.

Full-stack rebuilds of the two forks landed in sync during this window. The riscv branch of the PyTorch fork completed a full-stack rebuild in the early hours of 10-11 (around 03:00): 23 local commits were re-landed with new committer timestamps (author dates spanning from April through 10-04, including the merged #1 blocklist, the CI and fix series for #4 / #11 / #12 / #18 / #20 / #21 / #40 ~ #44, the #50 blocklist expansion, and three SyncBots integration records), with the head remaining “[SyncBots] Integrate PyTorch at e188cec” and the base advancing with upstream (including upstream commits from 10-10). The riscv branch of the LLVM fork completed another nightly replay late on 10-11 (around 23:00): 26 local patches were re-landed wholesale with new committer timestamps, with the head still #31 “A100 HP/SP and pack/unpack lowering and scheduling calibration”, the stack composition unchanged from the previous round, and the replay anchor synced to the 10-11 upstream snapshot. After the rebuilds / replays on both sides completed, the baseline records for their respective open PRs (8 for PyTorch, the two FPGA PRs #25 / #28 for LLVM) were refreshed in turn, awaiting the next round of review.

On the Triton side, the Buddy MLIR dependency upgrade PR #84, unblocked in the previous window, was merged on the afternoon of 10-10 (13:31) (auto-merged by bot): the PR had been open since 09-20, upgrading buddy-mlir to the nightly version v0.0.11.dev20260925; it had previously failed to build because the new LLVM shipped with v0.0.11 was incompatible with the pinned frontend API, and became mergeable after the patch adaptation (#86) on 10-09 cleared the way. The chain “patch adaptation (#86) → dependency upgrade (#84)” is now closed; the next things to watch are whether the nightly channel produces a new build containing v0.0.11, and the review progress of the community software optimization PR #85.

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

Window Overview: The RuyiAI-Stack organization has 18 repositories, with five actions in this window: pytorch (full-stack rebuild on the riscv branch with 23 re-landed commits; baseline refresh of 8 open PRs; 55 upstream syncs on main), llvm-project (nightly replay of 26 commits on the riscv branch; refresh of two FPGA PRs), triton-riscv (#84 merged), harness (1 commit: Triton-RISCV plugin backend), and ruyiai-daily (issues 10-11) plus the site repository (2 routine commits); tilelang-riscv, mxnet, caffe, FBGEMM, IntrinTrans, VecIntrinBench, cpuinfo, torq-tile, dsh-osc, skills, pytorch-ci, SyncBots-DeepAgents and others had no pushes in this window.

1.1 pytorch: riscv branch completes full-stack rebuild (23 re-landed commits); routine baseline refresh of 8 open PRs (10-11)

Date: 2026-10-11　Source: riscv branch commit list, head commit 0fc3546d, rebuild sample commit 9434cbce, PR list

The riscv branch completed a full-stack rebuild in the early hours of 10-11 (around 03:00): 23 local commits were re-landed with new committer timestamps, with the head retaining the “[SyncBots] Integrate PyTorch at e188cec” integration line (author date 10-04), below which are the local patches and CI commits in their existing order (#44 bytes_to_scalar fix, #50 expanded blocklist, #42 ULP tolerance, three SyncBots integrations, #40 / #41 CI parsing, #20 / #21 CI split, #18 cpuinfo replacement, #12 commit hash pinning, #11 blocklist, #4 blocklist format, #1 initial blocklist, etc.), with the base carrying the 10-10 upstream snapshot. This round is another iteration since the branch’s rebuild in the early hours of 10-08 (machine timestamps clustered, author dates earlier than the window — a routine rebuild rather than new development). On the open PR side: 8 PRs (#23 Enable XNNPACK, #35 test PR, #36 timeout relaxation, #38 DataLoader temporary disable, #43 patch trimming, #46 ATen RVV support, #48 RVV CPU capability, #51 riscv64 local image) were batch-refreshed on the morning of 10-11 (09:10) (continuing the routine baseline sync cadence), all remaining open, with no merges or closures in this window. The main branch included 55 upstream commits in this window (sampled as general changes to inductor, dynamo, ROCm, etc., not individually recorded per the filtering rules).

1.2 llvm-project: riscv branch completes another nightly replay (26 commits); two FPGA PRs refreshed and awaiting review (10-11)

Date: 2026-10-11　Source: riscv commit list, head commit a2a364a1, PR #25, PR #28

The riscv branch completed another full replay of the patch stack late on 10-11 (around 23:00): 26 local patches were re-landed with new committer timestamps, with the head a2a364a1 still being #31 “A100 HP/SP and pack/unpack lowering and scheduling calibration” (same title as the previous round’s head — a routine replay); the stack composition remains the existing 26 commits (including #30 “IME intrinsics lowering to SpacemiT A100 dot instructions”, #29 BOSC AME instruction update, #27 xtame design, #24 BOSC AME backend design, #23 XBuckyball instruction carrier, #20 Buckyball vendor extension, #18 / #16 / #14 etc., plus the SyncBots integration record). The branch base includes upstream commits from 10-11 (around UTC 14:49), meaning this replay brought in the latest upstream snapshot in sync (this round follows the one late on 10-09). After the replay completed, the update times of the two FPGA backend PRs (#25 “BOSCAME FPGA backend”, #28 “xboscame FPGA”) were refreshed at 10-12 00:55, remaining open and awaiting review. Note: the buckyball branch (head from 10-06) had no new activity in this window.

1.3 triton-riscv: #84 Buddy MLIR dependency upgrade merged; #85 remains open (10-10)

Date: 2026-10-10　Source: PR #84, merge commit fe554ffa, PR #85, Releases page

The only new commit on the main branch in this window was the merge of #84 (10-10 13:31, commit fe554ffa; background and details in today’s highlights). With the dependency upgrade in place, the frontend’s pairing with Buddy MLIR is closed on the v0.0.11 line (nightly build dev20260925). On the open PR side: community contributor #85 (softmax and matmul optimization) had no updates in this window and remains open; the other open PRs (#83, #56, #54, #58, #55, #82, etc.) had no activity. On the nightly channel side, there was no new build, with the most recent still being “Nightly 2026-10-04-12c2f6a” (covering six sub-builds for CPython 3.12 / 3.13 / 3.14 on x86_64 and riscv64, deferred per the existing weekly cadence).

1.4 harness: Triton-RISCV plugin adds MySQL persistence, Redis cache, and RabbitMQ worker (10-10)

Date: 2026-10-10　Source: PR #3, merge commit e132bf25

The R&D infrastructure repository harness landed a relatively large commit (10-10 13:28, author ada-cl25; 82 files, +4228 / -1152): adding MySQL persistence, guarded Redis caching, and a RabbitMQ task worker to plugins/triton-riscv, and wiring the Python backend tests into a Vitest-driven CI service (the form notes several CI environment fixes and Redis configuration additions). This is a productionization enhancement of the harness-side Triton-RISCV agent toolchain in the “control plane — task queue — persistence” direction; the merge was picked up the same day by ruyiai-daily issue 10-11 (see 1.5).

1.5 Intelligence and site infrastructure: ruyiai-daily publishes issue 10-11; two routine commits to the site repository (10-11 ~ 10-12)

Date: 2026-10-11 ~ 2026-10-12　Source: issue 10-11 commit ad7343ad, issue 10-11 file, site commit 6e2ef1ea, site commit caee0560

The technology intelligence repository’s issue 10-11 (pushed 10-11 06:13) went live on the morning cadence, with a self-reported window of 10-10 04:52 ~ 10-11 06:00: highlights include LLVM Scudo’s quarantine batch bounds checking in release builds (#230247), progress on the HexFloat floating-point design discussion, M5Stack ToughC5 (ESP32-C5), etc.; the Triton and TileLang section covers harness #3 (MySQL / Redis / RabbitMQ, see 1.4) and tilelang’s SM121 block-scaled MMA (#3430), etc.; the RISC-V section covers XiangShan’s hybrid compressed ROB (#6648), riscv-arch-test storage tests (#2601), riscv-unified-db’s RVA23.1 / RVB23.1 profiles (#2721) and Zabha atomic path fix (#2566), SG2042 console (zsbl), etc. Issue 10-12 had not been pushed as of this window. The site repository had two routine contributors.json commits in this window (10-11 03:46, 10-12 03:55), with no new posts on the RuyiAI website or blog.

II. RuyiSDK Toolchain and Distributions (Build, Toolchain, IDE, openRuyi)

Window Overview: Within the ruyisdk organization window, two sets of activity: riscv-gcc (a single batch of 51 commits from ztt-dev) and the VS Code extension (PR #263 opened); on the release side, ruyi-imager nightly channel refreshed; ruyi, packages-index, support-matrix, board-docs, ruyi-tuner, riscv-binutils, riscv-gnu-toolchain, qemu, AME-operator, sail-riscv, riscv-isa-sim and others had no commits or releases within the window. Within the openRuyi-Project organization, two sets of activity: 5 commits in the main repository and 10 in lookout.

2.1 riscv-gcc: Single Batch of 51 Ztt Backend Commits on ztt-dev Branch (10-11)

Date: 2026-10-11　Source: ztt-dev commit list, head commit a326bc3, commit b3bb6cb1, commit 076f292f

On the afternoon of 10-11 (13:50), the ztt-dev branch advanced a single batch of 51 commits (author pz9115), focused on performance-oriented refinement and wrap-up of the descriptor system around the Ztt draft extension: descriptor reuse and caching (TC / ACC / zip / row-column / constructors, consumer and unary operand state, raw descriptor operation tracking), indexed lookups (builtin decoders, store declarations, overload candidates, profile and type lookups), zero-value and narrow-carrier simplification (zero register reuse, narrow scalar carriers, floating-point zero-offset shift folding), branch edge and fallthrough propagation, post-DCE cleanup, dynamic workspace factorization, LTO dump and optimized instruction check updates (details in today’s highlights). The rest of the organization’s toolchain repositories remained silent: riscv-binutils’ ztt-dev (latest 09-30) and riscv-gnu-toolchain’s ame-experimental (09-30) had no commits within the window; riscv-gcc’s other branches (16.2, p-rebase) saw no new activity; no PR activity within the window (most recent merges #20 / #21 were on 10-07).

2.2 VS Code Extension: PR #263 Opened; #262 Remains Open (10-10)

Date: 2026-10-10　Source: PR #263, PR #262, Releases page

PR #263 “feat: show a message when using a too low ruyi version” was opened by sisungo on the morning of 10-10 (10:52): it gives a clear prompt when the ruyi version used by the workspace is lower than required, pointing to the extension’s version prerequisite check for new ruyi capabilities (such as the device installation pipeline). #262 (build module unit tests), opened in the previous period, remains open with no updates within the window. On the release side, 0.1.7 is still the latest version.

2.3 openRuyi: 5 Commits Landed Including docker-cli; lookout Inspection Pipeline Expanded (10-10 ~ 10-11)

Date: 2026-10-10 ~ 2026-10-11　Source: openRuyi commit list, commit e53047d6, commit 7bd4afd7, lookout commit list

5 commits in the main repository within the window: added the docker-cli package definition and moved moby’s Provides into docker-cli, fixed the PR template link, upgraded openssl to 3.6.5, upgraded go to 1.27.2 — following the earlier Go ecosystem batch, the container toolchain and base packages continue to be filled in. The upstream inspection tool lookout (self-described as “tracking openRuyi’s package versions, builds, and upstream maintenance data”) had 10 commits within the window (10-10 ~ 10-11, author Jingwiw): discovering Go components from trusted source tags, observing Go language requirements with precise release data and aligning module identity with source versions, adopting trusted release versions for PyPI sources, supplementing verified NVD product identities, expanding lifecycle (EOL) coverage for openRuyi packages, preserving confirmed SPEC evidence when refreshes are interrupted, stamping mirror versions onto application metadata, etc. — the inspection pipeline expanded from version-facing to security- and lifecycle-facing, providing verification infrastructure for packaging expansion.

2.4 Others: ruyi and PyPI Remain at 0.53.0; ruyi-imager Nightly Channel Routinely Refreshed (10-11)

Date: 2026-10-11 (status)　Source: ruyi Releases, PyPI, Imager nightly build

ruyi package manager: main repository silent (latest commit 09-25, no PR activity within the window); PyPI 0.53.0 remains the latest (uploaded 09-24, no new beta). ruyi-imager: nightly channel build routinely refreshed (10-11 05:37, no code changes). packages-index, support-matrix, board-docs, ruyi-tuner and others saw no new activity in this window.

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

3.1 Three Repositories Silent; MXNet / Caffe Open PRs Total 18 with No Window Updates (10-11 status)

Date: 2026-10-11 (status)　Source: VecIntrinBench, IntrinTrans, FBGEMM fork, MXNet PR list, Caffe PR list

The three target repositories for vector intrinsic benchmarks, intrinsic translation, and low-precision operator libraries remain silent (VecIntrinBench last commit 02-13, IntrinTrans 06-25, FBGEMM fork 07-13); the same group’s cpuinfo (05-20) and torq-tile (04-09) saw no activity. The open PR counts for the two classic framework repositories remain unchanged: MXNet 15 (latest update 09-24), Caffe 3 (09-28), totaling 18, with no updates within the window. The compilation and operator chain activity in this window is concentrated in riscv-gcc’s Ztt line (see 2.1) and the full-stack rebuilds of the two forks (see 1.1 / 1.2).

IV. Community and Events (Biweekly Report, Forum)

4.1 No New Forum Posts Within the Window; Biweekly Report Remains at Issue 077 (10-11 status)

Date: 2026-10-11 (status)　Source: RuyiSDK Developer Community, #2886, #2852

No new topics or replies within the forum window; the latest topic remains #2886 from 10-08, “Hands-on Notes on Installing and Upgrading ruyi with a Script.” The RuyiSDK Biweekly Report Issue 077 (09-24) remains the latest, with Issue 078 not yet published; the RuyiAI section has no new posts. Community activity was at a low level over the two weekend days.

4.2 Zero Hits for External News and arXiv; No New Articles on the openRuyi News Page (10-11 status)

Date: 2026-10-11 (status)　Source: openRuyi news page, arXiv, RuyiAI official site

Google News returned zero relevant hits within the window for multiple Chinese and English queries on RuyiSDK, RuyiAI, openRuyi, and “如意 RISC-V” (general RISC-V queries returned normally during the same period, so the channel is not anomalous). arXiv (RISC-V and compilation, vector, inference directions) had no new entries within the window (the most recent related items were the 10-06 “RISC-V Transformer Inference Acceleration Framework for Edge AI” and a 10-07 entry, both before this window). The openRuyi distribution news page has no new articles (the 2026.09 release announcement remains the latest); the RuyiAI official site and blog have no new articles.

V. Trend Observations

5.1 Dual-Track Rebuild Cadence: Two Forks Each Complete a Full-Stack Rebuild in the Same Week

Within this window, the riscv branches of both the PyTorch and LLVM forks each completed a full-stack rebuild: PyTorch with 23 re-landed commits (early hours of 10-11), LLVM with 26 replayed commits (late night of 10-11), with each fork’s open PR baseline refreshed accordingly — “upstream advance → full-stack replay → PR baseline refresh” has become the normalized operational pattern on both forks (this round being PyTorch’s next after 10-08 and LLVM’s next after 10-09). Watch points: a rebuild only guarantees the same baseline as upstream; actual content progress still depends on the efficiency of PR review (LLVM’s two FPGA PRs, PyTorch’s RVV series).

5.2 Ztt Line Accelerates for a Second Consecutive Batch: Single-Batch Size 36 → 51 Commits

The GCC backend line of the Ztt draft matrix expansion has picked up pace since its establishment on 09-30: after 36 commits on 10-08 alone, this window landed another 51 commits (the largest single batch), with the theme shifting from feature scaffolding to performance-oriented refinement of the descriptor system (reuse, caching, indexing, and workspace factorization) — typically signaling that the feature surface is stabilizing and the work is entering the optimization and wrap-up phase. Watch points: follow-through on ztt-dev on the riscv-binutils side (currently still stalled at 09-30) and the upstreaming path.

5.3 Dependency Upgrade Chain Closes: #86 Adaptation → #84 Merge

The previous window cleared the way for the new LLVM API with the #86 patch adaptation; in this window #84 was merged immediately after, landing the Buddy MLIR v0.0.11 dependency upgrade — the Triton-RISCV frontend has once again completed a full loop in the adaptation chain between “rapid LLVM upstream evolution — pinned frontend — dependency upgrade.” Follow-up watch points: whether the nightly channel produces a new build containing v0.0.11 (the latest is still the 10-04 edition); review of community optimization PR #85 (softmax and matmul paths); and the evolution of the A100 / BOSC AME patches in the LLVM stack during the next replay round.

Source Verification Table

Source Verification Result
RuyiAI-Stack org (all repos) pytorch: riscv full-stack rebuild (23 commits) + 8 PR baseline refreshes + 55 upstream main commits; llvm-project: riscv nightly replay (26 commits) + two FPGA PR refreshes; triton-riscv: #84 merged; harness: 1 commit (MySQL / Redis / RabbitMQ); ruyiai-daily 10-11 edition; site repo 2 routine commits; no pushes to tilelang-riscv, mxnet, caffe, FBGEMM, etc.
ruyisdk org (all repos) riscv-gcc: ztt-dev single batch of 51 commits; VS Code extension PR #263 opened; ruyi-imager nightly channel refreshed; no window activity in ruyi, packages-index, support-matrix, board-docs, ruyi-tuner, riscv-binutils, etc.
openRuyi-Project org (all repos) Main repo 5 commits (docker-cli, openssl 3.6.5, go 1.27.2, etc.); lookout 10 commits (Go / PyPI / NVD and EOL verification pipeline); no window activity in remaining repos
RuyiSDK Community Forum No new topics or replies (latest topic 10-08); biweekly report remains at issue 077; no new posts in the RuyiAI section
openRuyi News Page No new articles (the 2026.09 release announcement remains the latest)
ruyi package manager / PyPI Main repo silent (latest 09-25); PyPI 0.53.0 remains the latest (uploaded 09-24)
Tech intelligence repo (ruyiai-daily) 10-11 edition pushed on the morning cadence; 10-12 edition not yet live
VS Code Extension PR #263 opened (ruyi version too low warning); #262 remains open; 0.1.7 still the latest release
arXiv (RISC-V compilation and vectorization) No new entries in the window (most recent related items 10-06 / 10-07)
Google News RSS (multiple Chinese and English queries) Zero relevant hits for RuyiSDK / RuyiAI / openRuyi / 如意 RISC-V; channel functioning normally
RuyiAI official site and blog No new blog posts (only 2 routine contributor data commits in the window)

Complete Source List