Research window: Past 3 days (2026-09-25 04:30 ~ 2026-09-28 04:30, Beijing time; the Monday window covers the weekend).

Sources: GitHub three-organization audit (commits and Releases across 18 repos in RuyiAI-Stack, 45 repos in ruyisdk, and 35 repos in openRuyi-Project, via both Atom and web channels; upstream fork commits filtered item by item against RISC-V keywords, with irrelevant commits excluded), RuyiTuner repository (Releases, CHANGELOG, branch commits), ruyi package manager and test submodule repositories, development board support matrix merge queue, RuyiSDK developer community (latest forum topics and the RuyiAI section), openRuyi distribution news page, arXiv search, PyPI version verification, and Google News RSS multi-query searches in both Chinese and English (via proxy; no hits in this window, see appendix).

Index for This Issue

  • Today’s Highlights: RuyiTuner v1.8 released, actual compilation comparison phase completed over the weekend, three-stage pipeline takes shape (09-25 ~ 09-27)
  • I. RuyiAI Stack Progress (PyTorch / Triton / TileLang RISC-V adaptation)
    • 1.1 Compiler fork silent: XTHeadVector fix PR #168 review stalled at 09-24, no activity on pre-research branch (09-28 status)
    • 1.2 triton-riscv: dependency PR #84 updated to buddy-mlir nightly dev20260925 (09-25)
    • 1.3 PyTorch fork: riscv branch and 8 open PRs remain at 09-21 status (09-28 status)
    • 1.4 Technical intelligence repository: ruyiai-daily has not pushed for four consecutive issues, latest remains the 09-23 issue (since 09-24)
  • II. RuyiSDK Toolchain and Distribution (kernel, support matrix, IDE, openRuyi)
    • 2.1 ruyi: test timeout calculated by package count PR #503 merged (09-25)
    • 2.2 Support matrix: ESP32C3 RT-Thread 5.3.1 report merged (PR #406, 09-27)
    • 2.3 VS Code extension: added “View Example” guidance (09-26)
    • 2.4 Official website: two routine automated updates merged for data interface and submodule (09-25)
    • 2.5 openRuyi: main repository silent, two compilation pool adjustments in ceph-ci, 2026.09 monthly release announcement not yet live (09-28 status)
  • III. Vector Extensions and Operator Optimization (VecIntrinBench / IntrinTrans / FBGEMM)
    • 3.1 Three dedicated target repositories remain silent within the window (09-28 status)
  • IV. Community and Events (biweekly report, forum)
    • 4.1 No new topics in the forum within the window, biweekly report issue 077 remains the latest (09-28 status)
    • 4.2 Zero hits for external news and arXiv (09-28 status)
  • V. Trend Observations
    • 5.1 Weekend exception: high-frequency iteration window for a solo maintainer
    • 5.2 “Release-maintenance” rhythm: main repository silent after 0.53.0
    • 5.3 The RT-Thread line of the support matrix continues to expand
    • 5.4 Gaps and points of attention in this window

Today’s Highlight: RuyiTuner v1.8 Released, Real-Compilation Comparison Stage Completed Over the Weekend, Three-Stage Pipeline Takes Shape

Date: 2026-09-25 ~ 2026-09-27　Source: v1.8 Release, CHANGELOG, real_compile split commit

RuyiTuner is the Ruyi community’s LLVM-oriented compiler tuning tool, which automatically searches for pass sequences that maximize code size reduction based on “optimization synergy analysis.” At 09:06 Beijing time on the morning of 09-25, the tool released v1.8 (tag pointing to commit a032c28c “Add ruyi-cc to use pass seq into project”). The updates consolidated in v1.8 relative to v1.7 (09-17) include: the --search_scope project mode for searching a common pass sequence across the entire project (aggregate-fitness GA), the --max-path-length parameter, and the scripts/ruyi-cc.sh compiler wrapper script—which plugs the optimal sequence into the project’s normal compilation flow (make CC=scripts/ruyi-cc.sh), with the sequence nested according to the scoring convention, code-generation options such as -fPIC / -mcmodel forwarded to llc, and full compilation, linking, and compress/decompress functional verification completed on bzip2-1.0.2. Of these, the project-level search and --max-path-length portions were tracked separately in earlier windows (09-22 / 09-24).

Development did not stop after the release: over two days, 09-25 (7 commits, 09:06 ~ 19:31) and 09-27 (6 commits, 16:11 ~ 18:22), the v1.x branch saw 13 consecutive commits (merged into main twice), advancing the 1.9 version line to the point where “real-compilation comparison” took shape—first persisting the project-level search sequence to disk (09-25 17:04), then adding the stage that “actually compiles the source with the optimal sequence and reports the size reduction rate” to the main entry point (18:27), and subsequently folding the capability in from the temporary wrapper script and deleting scripts/ruyi-cc.sh (19:31); on 09-27 the stage was split into a standalone script real_compile.py (18:10), forming a three-stage pipeline together with train.py and run.py (stage titles 1/3 through 3/3), and completing: renumbering outputs by stage (enumeration files changed to the Step1 prefix, sequences and results changed to the Step2 prefix), no longer persisting intermediate files for synergy-pair lookup (switched to in-memory passing), --dataset supporting a single .c / .i source file, the GA’s obj-size scoring switching to the pic relocation model (aligning with clang’s default convention on x86_64), the real-compilation stage reusing the C→IR cached .ll files, extracting x86 / RISC-V code size data by project, and updating the schematic diagram to V2.0.

As of the end of the window, 1.9 has not yet been released (the latest Release is still v1.8), and its changes have been fully written into the CHANGELOG “1.9 version changes” section; the tool’s version and architecture generality remain unchanged (not bound to an LLVM version or target architecture, with the target determined by the target triple of the input IR). This round of refactoring consolidated the previous form of “two-stage search + external compilation wrapper script” into a built-in three-stage pipeline.

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

Window Overview: Among the 18 repositories in the RuyiAI-Stack organization, only the site repository ruyiai-stack.github.io had 3 routine contributor data commits during the window (one per day from 09-25 to 09-27); pytorch, triton-riscv (main branch), llvm-project, tilelang-riscv, FBGEMM, cpuinfo, VecIntrinBench, IntrinTrans, harness, dsh-osc, torq-tile, skills, pytorch-ci, SyncBots-DeepAgents, mxnet, and caffe all had no pushes during the window.

1.1 Compiler Fork Silent: XTHeadVector Fix PR #168 Review Stalled at 09-24, Pre-Research Branches Inactive (09-28 Status)

Date: 2026-09-24 (status)　Source: Branch list, PR #168

No new commits were seen in ruyisdk/llvm-project during the window: neither the main branch nor the three matrix extension pre-research branches AME, riscv-ime-preview, and ame0p6 saw any activity during the window; the last review and CI activity on the XuanTie vector mixed-width indexed memory access fix PR #168 (opened 09-24) stalled on the day it was opened, with no new progress during the window. The dual-track pace of “matrix extension pre-research + XTHeadVector maintenance” from last week’s window has temporarily frozen in this window.

1.2 triton-riscv: Dependency PR #84 Updated to buddy-mlir Nightly dev20260925 (09-25)

Date: 2026-09-25　Source: PR #84, PR list

The triton-riscv main branch had no commits during the window; the renovate bot’s dependency-tracking PR #84 continued to advance with nightly builds during the window—the buddy-mlir reference was updated to nightly/v0.0.11.dev20260925 (Beijing time on the evening of 09-25, PR remains open). On the feature side, the update times of 6 conversion and example PRs (#83, #56, #54, #58, #55, #82) remain stalled at 09-15 ~ 09-17, with no new reviews during the window.

1.3 PyTorch Fork: riscv Branch and 8 Open PRs Maintain 09-21 Status (09-28 Status)

Date: 2026-09-21 (status)　Source: riscv branch commits, PR list

The fork’s riscv branch had no new commits during the window (the branch head remains at a batch from the evening of 09-20); the update timestamps of all 8 open PRs (#23, #35, #36, #38, #43, #46, #48, #51) remain stalled at 09-21, with no changes during the window; among them, the queue time for the two RVV-direction PRs (#46 ATen RVV support, #48 RVV CPU capability) continues to accumulate.

1.4 Tech Intelligence Repository: ruyiai-daily Misses Four Consecutive Issues, Latest Still the 09-23 Issue (from 09-24)

Date: 2026-09-24 ~ 09-27 (gap period)　Source: ruyiai-daily commit history

The tech intelligence repository ruyiai-daily had no new issue pushed during the window: the latest issue remains the 09-23 issue (committed on the morning of 09-23), with four consecutive issues absent from 09-24 to 09-27. The repository had previously maintained consecutive daily pushes from 09-18 to 09-23; this gap has widened for a second consecutive window, and subsequent windows will be needed to confirm whether this is a cadence adjustment or a discontinuation.

II. RuyiSDK Toolchain and Distribution (Kernel, Support Matrix, IDE, openRuyi)

Window Overview: Of the 45 repositories in the ruyisdk organization, 5 saw activity during the window: ruyi-tuner (v1.8 release and 15 commits, see Today’s Highlights), ruyi (PR #503 merged), support-matrix (PR #406 merged), ruyisdk-vscode-extension (1 commit), and ruyisdk-website (2 automated updates); llvm-project, riscv-gcc, linux-xuantie-kernel, ruyi-backend, docs, board-docs, packages-index, wechat-articles, and others had no new commits during the window.

2.1 ruyi: Test Timeout Calculated by Package Count, PR #503 Merged (09-25)

Date: 2026-09-25　Source: PR #503, merge commit 237311e3, ruyi-pytest commit 94881c0b

At 21:06 Beijing time on 09-25, PR #503 “tests(ruyi-pytest): calculate ruyi install timeout by pkg count” was merged by maintainer xen0n. The PR updates only one line: advancing the test submodule tests/ruyi-pytest reference from c48823c5 to 94881c0b; the latter corresponds to the test repository’s 09-24 commit—changing the package manager test suite’s install timeout to be calculated by the number of packages installed, replacing the fixed timeout value, reducing sporadic timeouts in multi-package scenarios. This is a small wrap-up step for the test line after the 0.53.0 release. During the window, the ruyi main repository had no other commits; the v0.53.x release branch has been silent since release; the latest Release remains 0.53.0 (09-24), PyPI 0.53.0 remains the latest, and the next version is previewed for late October (see issue 077).

2.2 Support Matrix: ESP32C3 RT-Thread 5.3.1 Report Merged (PR #406, 09-27)

Date: 2026-09-27　Source: PR #406, report commit cf6af500, min_rev commit 41235259

At 11:26 Beijing time on 09-27, PR #406 “ESP32C3: add RT-Thread 5.3.1 test report” was merged (two commits). The report was submitted by contributor Chen Moushun: ESP32-C3-DevKitM-1 (rev v1.1) runs RT-Thread on the official ESP32_C3 BSP and enters msh; the test commit is pinned to dc3da6d8 (the serial banner shows 5.3.1, not the v5.3.1 release tag); the documentation records two board-level details—a linker script change on the Windows side, and the handling of esptool’s min_rev (the board’s default image header min_rev=3 would be rejected, requiring the onboard bootloader.bin’s min_rev to be set to 0, with the esptool snippet used attached). A total of 306 lines of new bilingual (Chinese-English) documentation were added. On the review queue side: #397 (RT-Thread Smart, Milk-V Duo S), #405 (Zephyr, Milk-V Duo S), and #390 (VisionFive2_Lite Ubuntu) remain open, with no new reviews during the window.

2.3 VS Code Extension: New “View Example” Guidance Added (09-26)

Date: 2026-09-26　Source: commit 0d61f1a0

At 13:37 Beijing time on 09-26, the extension repository merged a feature commit “feat: add ‘View Example’ when found no build rules” (contributor sisungo): when no build rules are found in the workspace, a new “View Example” entry is added to the interface to guide users to view examples; along with this, the Chinese and English localization strings were updated and redundant entries cleaned up (two l10n files and build.service.ts, totaling +20 / -12 lines).

2.4 Website: Two Routine Automated Updates Merged for Data Interface and Submodule (09-25)

Date: 2026-09-25　Source: commit 2ffc6b4d, commit 499dd18a

At 11:26 Beijing time on 09-25, two routine automated updates were merged in the website repository: a data interface update (#592) and a submodule reference update (#591), both produced by automated tasks.

2.5 openRuyi: Main Repository Silent, Two ceph-ci Build Pool Adjustments, 2026.09 Monthly Announcement Not Yet Live (09-28 status)

Date: 2026-09-25　Source: ceph-ci commit b41d2806, openRuyi news page

The openRuyi distribution main repository was silent during the window (the most recent commit is the 09-24 desktop dependency fix, which belongs to the previous window); within the openRuyi-Project organization, only ceph-ci saw activity—two commits on the evening of 09-25 Beijing time, capping the non-ASan ninja build concurrency pool at 24, plus one file cleanup (contributor sunyuechi). There is no new announcement on the distribution news page: the 2026.08 monthly release (released 08-27) remains the latest, and the 2026.09 monthly announcement is not yet live; following the end-of-month release cadence of 05-29 / 06-30 / 07-23 / 08-27, the announcement window is approaching.

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

3.1 Three Dedicated Target Repositories Remain Silent During the Window (09-28 status)

Date: 2026-09-28 (status)　Source: VecIntrinBench, IntrinTrans, FBGEMM

All three repositories—targeting vector intrinsic benchmarks, intrinsic translation, and low-precision operator libraries—had no commits during the window: VecIntrinBench’s last commit was 02-13, IntrinTrans’s was 06-25, and the FBGEMM fork’s was 07-13; the same group’s observation targets cpuinfo (05-20) and torq-tile (04-09) were likewise silent. Activity related to “code size and sequence optimization” in this window is concentrated in RuyiTuner’s real-compilation comparison line (see Today’s Highlights).

IV. Community and Events (Biweekly Report, Forum)

4.1 No New Topics on the Forum During the Window, Biweekly Report Issue 077 Remains the Latest (09-28 status)

Date: 2026-09-28 (status)　Source: latest forum topics, Issue 077 release post

There were no new topics on the RuyiSDK developer community forum during the window (09-25 to 09-27): the latest topics remain the Issue 077 biweekly report released on 09-24 (#2852) and the 09-24 open-source tech hotspot news post (#2851); the daily news post series was not updated during this window (the most recent post is from 09-24). The next biweekly report issue is not yet live.

4.2 External News and arXiv: Zero Hits (09-28 status)

Date: 2026-09-28 (status)　Source: Multiple Google News RSS queries (via proxy), arXiv search

Multiple Chinese-language Google News queries (when:3d) for RuyiSDK, RuyiAI, openRuyi, and 如意 RISC-V all returned zero hits; a bare query verified the channel is working (RuyiSDK returns only historical entries from 2024). arXiv searches (RISC-V with vector / compiler / inference directions) had no new entries during the window, with the most recent being the 09-24 “Compiler and Hardware Co-Design for Accelerator Architectures”.

V. Trend Observations

5.1 Weekend Exception: A High-Frequency Iteration Window for a Solo Maintainer

RuyiTuner was the only high-frequency development surface in this window — on 09-25 and 09-27, the same maintainer pushed 13 consecutive commits and merged into main twice, closing out a cross-window refactor (from a temporary compile wrapper script to a built-in real compilation stage) into a three-stage pipeline. Looking back at the release cadence: v1.6 (08-31) to v1.7 (09-17) spanned about two and a half weeks, v1.7 to v1.8 (09-25) took 8 days, and 1.9 changes are already in flight — the tooling line iterates at a “usable increment per week” pace, in contrast to the quiet of the main stack in this new window.

5.2 “Release-Maintain” Cadence: Main Repo Silent After 0.53.0

In the first full window after the ruyi 0.53.0 release (09-24), the main repo saw only one test submodule follow-up (#503); the three issues related to the 0.53 release cycle (#495, #498, #501) are all now closed, leaving only the long-term tracking item #401 (PyPI installation readiness tracking on RISC-V) still open. Combined with the preview in issue 077 of “next version at the end of October,” we are currently in a quiet maintenance stretch between versions — release quality focus shifts to community installation feedback.

5.3 The RT-Thread Line of the Support Matrix Continues to Expand

The only merge into the support matrix in this window was the RT-Thread 5.3.1 report for ESP32-C3; over the past two weeks, the matrix’s RISC-V board coverage has come mostly from the two RTOSes RT-Thread and Zephyr (CH32V307 and ESP32-C3 updated consecutively), while three entries for the Milk-V Duo S platform (RT-Thread / RT-Thread Smart / Zephyr) remain queued. The OS-level test catalog for RISC-V development boards continues to densify.

5.4 Gaps and Focus Points in This Window

Gaps: the RuyiAI-Stack main stack (pytorch / triton-riscv / llvm-project and other feature lines) has been silent for a second consecutive week, with the divergence between the framework side waiting and the tooling side running hot now in its second week; the technology intelligence repository is in its second week of interruption (four consecutive issues absent since the 09-24 issue); the forum and external news sides are entirely silent. Focus points: first, the openRuyi 2026.09 monthly release announcement (end-of-month window); second, the merge cadence of the three pending support matrix entries; third, the follow-up content of llvm-project PR #168 and the two pre-research branches; fourth, whether ruyiai-daily resumes publishing; fifth, community feedback on ruyi 0.53.0 and new issue activity.

Source Verification Table

Source Verification Result
RuyiAI-Stack organization (18 repos) Only ruyiai-stack.github.io had routine activity (3 contributor data commits); pytorch, tilelang-riscv, llvm-project, FBGEMM, cpuinfo, VecIntrinBench, IntrinTrans, harness, dsh-osc, torq-tile, skills, pytorch-ci, etc. had no pushes in the window (triton-riscv dependency PR has updates, see 1.2)
ruyisdk organization (45 repos) ruyi-tuner (v1.8 release and 15 commits), ruyi (#503 merged), support-matrix (#406 merged), ruyisdk-vscode-extension (1 commit), ruyisdk-website (2 automated updates) had activity; the rest (llvm-project, riscv-gcc, linux-xuantie-kernel, ruyi-backend, docs, board-docs, packages-index, wechat-articles, etc.) had no new commits
openRuyi-Project organization (35 repos) Only ceph-ci had 2 commits (build pool adjustments); the openRuyi main repo, fwts, kvm-unit-tests, homepage, etc. had no pushes in the window
RuyiSDK Community Forum No new topics in the window (latest remains the 09-24 issue 077 and news post)
Biweekly Report Issue 077 remains the latest (published 09-24); the next issue is not yet online
openRuyi News Page No new announcements (2026.08 remains the latest; 2026.09 not yet online)
Development Board Support Matrix #406 merged (ESP32C3 RT-Thread 5.3.1); #397, #405, #390 under review
ruyi Package Manager Repo PR #503 merged; no other commits on main; latest Release 0.53.0 (09-24)
Technology Intelligence Repository (ruyiai-daily) Four consecutive issues unpublished since the 09-24 issue (latest is the 09-23 issue)
arXiv (RISC-V vector and AI compilers) No new entries in the window (most recent entry 09-24)
Google News RSS (multiple Chinese and English groups + bare queries) Zero hits for RuyiSDK, RuyiAI, openRuyi, Ruyi RISC-V; control queries returned normally, ruling out a scraping failure

Complete Source List