Research window: 2026-10-16 04:30 ~ 2026-10-19 04:30 (Beijing time, past 3 days, covering Saturday and Sunday).

Sources: Full-repository checks across three GitHub organizations (commits, pull requests, and releases in RuyiAI-Stack, ruyisdk, and openRuyi-Project, with every item in the window reviewed individually; upstream forks filtered by RISC-V keywords, with unrelated commits excluded), the buddy-compiler organization (buddy-mlir commits and stable/nightly releases), ruyi package manager and PyPI version verification, the openRuyi distribution news page, the RuyiSDK developer community forum, three consecutive issues of the ruyiai-daily technical intelligence repository, arXiv searches, and multiple Chinese and English Google News RSS queries (via proxy; external hits are listed in 5.3).

This Issue’s Index

  • Today’s Focus: BUDDY MLIR 0.1.1 Released — RISC-V Server-Side Cross-Compilation and Model Publishing Pipeline Land (10-18)
  • I. RuyiAI Stack Progress (PyTorch / Triton / TileLang RISC-V Adaptation)
    • 1.1 pytorch: 143 merges into the riscv branch within the window, 24 local patch-stack commits replayed in a batch; PR #51 merged (10-18)
    • 1.2 llvm-project: riscv branch has had no replays for six days since 10-12; two FPGA PRs stalled (10-18 status)
    • 1.3 tilelang-riscv: five RISC-V commits in a single day — operator runtime adaptation and Buddy MLIR release CI (10-16)
    • 1.4 triton-riscv: adapted to LLVM 24 and pinned Buddy MLIR v0.1.0, upgraded to nightly the next day (10-17, 10-18)
  • II. RuyiSDK Toolchain and Distributions (Firmware, Kernel, openRuyi)
    • 2.1 ruyi package manager: 0.53.0 maintained, 0.54.0 slated for end of October (10-16 status)
    • 2.2 openRuyi: six Rust RISC-V embedded packages added to SPECS (10-16)
    • 2.3 Kernel line: linux-xuantie-kernel adds profile extension probing, extension IDs aligned with upstream (10-16)
    • 2.4 Support matrix and tools: Milk-V Duo S dual-system test report merged, three VS Code extension improvements (10-16)
    • 2.5 Firmware line: no new Ruyi Firmware release for three consecutive days after 20261015 (10-16 to 10-18 status)
  • III. Vector Extensions and Operator Optimization (VecIntrinBench / IntrinTrans / FBGEMM)
    • 3.1 Three repos silent, no new progress on vector benchmarks or translation toolchain (10-18 status)
    • 3.2 Operator coverage evidence: triton-riscv self-test results under the LLVM 24 / Buddy MLIR 0.1.0 combination (10-18)
  • IV. Buddy Compiler Updates (buddy-mlir Commits and Releases)
    • 4.1 BUDDY MLIR 0.1.1: two changes — RISC-V server-side cross-compilation and model publishing workflow (10-18)
    • 4.2 Release cadence: stable releases every two days, nightly builds daily (10-16 to 10-18)
  • V. Community, Events, and Official Homepage
    • 5.1 The 6th RISC-V China Summit opens 10-18 in Shenzhen, RuyiSDK hosts booth D15 and talks (10-18)
    • 5.2 Official site and intelligence repo: three official homepage pages unchanged, intelligence repo publishes three issues in a row (10-16 to 10-18)
    • 5.3 Forum and external news: zero new forum posts, zero hits on targeted Google News queries (10-16 to 10-18)
  • VI. Trend Observations
    • 6.1 Compiler stack version coupling tightens: Buddy MLIR releases two versions in two days, downstream follows same-day
    • 6.2 Two fork maintenance lines continue to diverge: PyTorch merges and replays in parallel, LLVM silent for six days
    • 6.3 RuyiSDK advances on three fronts: kernel probing completed, distribution expanded, toolchain awaiting version window

Today’s Focus: BUDDY MLIR 0.1.1 Released — RISC-V Server-Side Cross-Compilation and Model Publishing Pipeline Land

Date: 2026-10-18　Sources: BUDDY MLIR 0.1.1 release page, 0.1.0 to 0.1.1 diff, PR #989 RISC-V server-side cross-compilation, PR #925 model publishing workflow

The main Buddy Compiler repo buddy-mlir released BUDDY MLIR 0.1.1 on 10-18 at 06:26 (Beijing time), roughly two days after 0.1.0 (10-16 00:53), making it the project’s second stable release in two days. Compared with 0.1.0, 0.1.1 contains only two changes across 24 files, about +896/-54 lines, both aimed at “deliverability.”

The first is #989 “add RISC-V server-side cross-compilation to buddy-server”: it adds a cross-compilation path targeting riscv64 for buddy-server, along with a handle implementation for the runtime dependency manifest (RaxDependenciesHandle, including unit tests and a test plugin), a stub implementation of plugin discovery and transcription tests, resolving runtime dependencies by manifest; it also streamlines buddy-cli (a net reduction of 40 lines) and updates the RVV environment documentation. The second is #925 “add publish-models workflow”: it adds a GitHub Actions publishing pipeline and a Hugging Face model publishing script (about 313 lines), enabling model artifacts to be pushed and published directly from CI. Together, 0.1.1 addresses both ends: “the server can run on RISC-V machines, and model artifacts can come out of CI.”

Downstream responded the same day: triton-riscv merged #87 on 10-17 22:41 to pin Buddy MLIR v0.1.0, then on 10-18 08:57 was upgraded to the v0.1.1 nightly by the automated version-tracking #88; tilelang-riscv added a Buddy MLIR release CI on 10-16 and builds the Python extension within that CI (see 1.3, 1.4, 4.1).

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

1.1 pytorch: 143 commits merged into the riscv branch within the window, 24 local patch-stack commits replayed as a batch; PR #51 merged (10-18)

Date: 2026-10-18　Sources: riscv branch commit list, head commit 8b254cfd, PR #51 riscv64 local image, PR list, two-round head comparison

The riscv branch saw 143 commits within the window, mostly upstream changes merged in daily by SyncBots (landing continuously from the early hours of 10-16 through all of 10-17); around 03:00 on 10-18, the local patch stack was replayed as a batch of 24 commits under a single committer timestamp, with the head updated to 8b254cfd “Add riscv64 image locally (#51)”, a difference of 269 commits versus the previous head 73ef01df (including upstream merges; 269 ahead, 23 behind, a divergence state following rebase).

On the merge side, the first PR merge in nearly five weeks appeared: PR #51 “riscv64 local image” was squash-merged at 00:04 on 10-17, adding .ci/docker/build-riscv64-local.sh (25 lines) and adjusting build and image scripts — the first merge since #50 on September 7. On the open-PR side, 7 PRs (#23 Enable XNNPACK, #35 for testing, #36 timeout relaxation, #38 temporary DataLoader disable, #43 patch trimming, #46 ATen RVV support, #48 RVV CPU capability) had their baselines batch-refreshed at 09:09 on 10-18 following the branch replay; all remain open with no new review comments.

1.2 llvm-project: riscv branch has had no replay for six days since 10-12; two FPGA PRs stalled (status as of 10-18)

Date: 2026-10-18 (status)　Sources: riscv branch commit list, PR list, PR #25 BOSCAME FPGA backend, PR #28 xboscame FPGA

The riscv branch head remains 0fb2da86 “[RISCV] Add A100 HP/SP and pack/unpack lowering with calibrated scheduling (#31)” (10-12 23:00 Beijing time); there have been no new commits for six consecutive days from 10-13 to 10-18, and the overnight replay has not restarted since 10-12. The two FPGA backend PRs (#25 “BOSCAME FPGA backend”, #28 “xboscame FPGA”) last updated on 10-12, with no review activity within the window. Upstream sync on the main branch continues as usual and is not itemized here per the filtering rules.

1.3 tilelang-riscv: five RISC-V commits in a single day — operator runtime adaptation and Buddy MLIR release CI (10-16)

Date: 2026-10-16　Sources: commit list, a314a8f3 codegen format specification, 6f980dbd upstream operator runtime semantics, 79b8ab17 Buddy MLIR release CI, 32fce5ed Python extension build

tilelang-riscv, previously silent for a long period, landed five commits in a burst between 15:56 and 18:52 on 10-16: first a314a8f3 to standardize the codegen format ahead of operator adaptation, then 6f980dbd “support upstream operator runtime semantics” and f1335f65 “upgrade TileOps runtime adaptation”, followed by 79b8ab17 adding the Buddy MLIR release CI and 32fce5ed building the Python extension within that CI. The chain extends from codegen regularization and operator semantic alignment to runtime adaptation and CI integration, and brings the official Buddy MLIR release artifacts into its own build process — the same direction as triton-riscv’s backend pinning strategy.

1.4 triton-riscv: adapts to LLVM 24 and pins Buddy MLIR v0.1.0, upgraded to nightly the next day (10-17, 10-18)

Date: 2026-10-18　Sources: PR #87 support LLVM 24 and pin Buddy MLIR v0.1.0, PR #88 upgrade to v0.1.1 nightly, commit list, Releases

PR #87 “[build] support LLVM 24 and pin Buddy MLIR v0.1.0” was merged at 22:41 on 10-17, handling triton-riscv’s compatibility with new LLVM symbol and inline-assembly interfaces and pinning the backend version to Buddy MLIR 0.1.0; the next day at 08:57, the automated version-tracking PR #88 upgraded the dependency to buddy-mlir nightly v0.1.1.dev20261017. These were the only two commits on the main branch within the window, both resulting from merges. triton-riscv’s own nightly release channel remains at “Nightly 2026-10-11-fe554ff” (launched 10-12), with no new build produced in this window.

II. RuyiSDK Toolchain and Distributions (Firmware, Kernel, openRuyi)

2.1 ruyi Package Manager: 0.53.0 Holds, 0.54.0 Slated for End of October (10-16 Status)

Date: 2026-10-16 (status)　Sources: ruyi Releases, PyPI ruyi, Biweekly Report No. 078

Both PyPI and GitHub Release remain at 0.53.0 (released 09-24), with no new versions or commits during the window. According to Biweekly Report No. 078 of 10-13, 0.54.0 is slated for the end of October due to a release-cycle adjustment; in-progress items include ABI compatibility checks between software packages and the current system, macOS packaging for more officially maintained software packages, and SpacemiT K1/K3 toolchain adaptation. Watch points: whether the end-of-month release window holds, and whether K1/K3 adaptation ships as a toolchain package or as preset configuration.

2.2 openRuyi: Six Rust RISC-V Embedded Packages Enter SPECS (10-16)

Date: 2026-10-16　Sources: openRuyi commit list, rust-riscv 0.16 commit 1cabeded, rust-embedded-hal 1 commit f120cade, rust-vcell 0.1 commit 8346109c

The openRuyi main repository saw two batches totaling 6 commits at 15:09 and 16:20 on 10-16, all new SPECS additions: rust-riscv 0.16, rust-riscv-macros 0.4, rust-riscv-types 0.1, rust-embedded-hal 1, rust-volatile-register 0.2, and rust-vcell 0.1. Judging from package names and dependencies, this group corresponds to the infrastructure for bare-metal Rust on RISC-V—register and CSR access macros (riscv-macros), type definitions (riscv-types), the embedded-hal abstraction, and volatile register and cell mutability support—as the distribution continues to fill out its packaging coverage of the Rust embedded stack. No new images were released for openRuyi during the window; 2026.09 remains the latest.

2.3 Kernel Line: linux-xuantie-kernel Adds Profile Extension Probing, Extension IDs Aligned with Upstream (10-16)

Date: 2026-10-16　Sources: linux-xuantie-kernel commit list, cpufeature profile extension commit 8fd30253, Zicclsm commit acc74e96, private ID segment commit 1b89fe6b

ruyisdk’s linux-xuantie-kernel (linux-6.6.36 branch) saw 4 commits during the window, all authored at 10-16 11:14 and landed as one batch: adding Ziccamoa, Ziccif, Ziccrse, Za64rs, and Zicclsm to cpufeature and hwprobe—the first four correspond to misaligned atomic access granularity, instruction-fetch atomicity, reserved-set, and 64-byte reserved-set guarantees respectively, while Zicclsm corresponds to support for misaligned accesses within a cache line, all capabilities required by the RVA20/RVA23 profiles; the other two commits carve out an ID segment for private extensions in hwcap and align the numbering with upstream. Combined with the previous issue’s unification of vendor extension keys into the XUANTIE_ form, XuanTie private extension naming and hwprobe exposure are gradually aligning with upstream rules.

2.4 Support Matrix and Tools: Milk-V Duo S Dual-System Test Reports Landed, Three VS Code Extension Improvements (10-16)

Date: 2026-10-16　Sources: support-matrix commit 2674d16d, Zephyr report commit 6f6acf05, ruyisdk-vscode-extension commit list, ruyi-imager nightly build

support-matrix added Zephyr and RT-Thread Smart test reports for the Milk-V Duo S at 11:37 and 11:46 on 10-16, continuing the direction of covering low-end RISC-V boards with RT-Thread / Zephyr. ruyisdk-vscode-extension saw three commits: a hint when a search returns no results, a warning when the ruyi version is too old, and unit tests for the build module (10-16 12:34 to 16:39). The ruyi-imager nightly channel updated its build at 10-18 04:34, with no commits in the main repository during the window.

2.5 Firmware Line: No New Releases for Three Consecutive Days After Ruyi Firmware 20261015 (10-16 to 10-18 Status)

Date: 2026-10-18 (status)　Sources: ruyifirmware Releases, edk2-ruyi commit list, coreboot k3/port commit list, openRuyi linux ruyi/7.3.y

The openRuyi firmware stack saw no commits during the window: ruyifirmware, edk2-ruyi, coreboot’s k3/port branch, opensbi’s k3/port branch, linux’s ruyi/7.3.y branch, and MultiArchUefiPkg’s riscv branch were all silent, with the latest release still “Ruyi Firmware 20261015” from 10-15. After three consecutive days of releases from 10-13 to 10-15, this line has gone quiet, in contrast to the dense iteration of the previous three issues; kernel-team-tools also saw no commits in the same period. Watch point: whether firmware iteration shifts to a cadence synchronized with images and the kernel.

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

3.1 Three Repositories Silent, No New Progress on Vector Benchmarks or the Translation Toolchain (10-18 Status)

Date: 2026-10-18 (status)　Sources: VecIntrinBench, IntrinTrans, FBGEMM fork

The three vector benchmark and translation toolchain repositories (VecIntrinBench, IntrinTrans, FBGEMM) saw no commits during the window, with their latest activity stopping at 02-13, 06-25, and 07-13 respectively; harness stopped at 10-10, cpuinfo at 05-20, and torq-tile at 04-09. Operator-side activity in this window was concentrated in triton-riscv and tilelang-riscv (see 1.3, 1.4), with no new data produced on the vector benchmark side.

3.2 Operator Coverage Evidence: triton-riscv Self-Test Results Under LLVM 24 / Buddy MLIR 0.1.0 (10-18)

Date: 2026-10-18　Sources: ruyiai-daily 10-18 issue, triton-riscv PR #87

The 10-18 issue of the technical intelligence repository recorded triton-riscv’s self-test data after completing adaptation to LLVM 24 and Buddy MLIR 0.1.0: 618 check-buddy items passed, 290 triton-shared items passed, and 9 expected failures; of the 3829 items covered locally by FlagGems, 10 native crashes remain, and some examples require a native RVV environment. The original text also notes that these are all the author’s local results and cannot be used to infer that full-model compatibility or all runtime validation on the RISC-V side has passed. For the operator stack, this data set defines the current usable boundary: the basic check chain is working, but operator coverage still has native crashes to clear.

IV. Buddy Compiler Updates (buddy-mlir Commits and Releases)

4.1 BUDDY MLIR 0.1.1: Two Changes — RISC-V Server-Side Cross-Compilation and Model Release Workflow (10-18)

Date: 2026-10-18　Source: Release page, Diff comparison, PR #989, PR #925 release workflow, Commit 60f354a7

The diff between 0.1.1 and 0.1.0 consists of just two commits, 24 files, and roughly +896/-54 lines: RISC-V server-side cross-compilation (#989) and the model release workflow (#925). The former adds a riscv64 cross-compilation path for buddy-server, introduces a runtime dependency handle (RaxDependenciesHandle) along with dependency manifest tests and a plugin-discovery stub, and also streamlines buddy-cli and updates the RVV environment documentation; the latter adds .github/workflows/publish-models.yml and a Hugging Face release script, bringing the release of model artifacts into CI. Together, the two changes complete both ends — server deployment and artifact delivery — and explain why 0.1.1 could ship just two days after 0.1.0 (the bulk of the content had already been frozen in 0.1.0).

4.2 Release Cadence: A Stable Release Every Two Days, Nightly Builds Daily (10-16 to 10-18)

Date: 2026-10-18　Source: buddy-mlir Releases, nightly v0.1.1.dev20261017, buddy-mlir commit list

Within the window, buddy-mlir produced three releases: nightly v0.1.1.dev20261016 at 07:11 on 10-16, nightly v0.1.1.dev20261017 at 07:24 on 10-17, and the stable release 0.1.1 at 06:26 on 10-18. The main branch saw only one commit in the window (#925, 10-16 09:35); the release content came mainly from changes already on the release branch. In terms of cadence, the gap from 0.0.11 (09-26) to 0.1.0 (10-16 00:53) was nearly three weeks, whereas 0.1.0 to 0.1.1 was only about two days — after the major version jump, the project shifted to small, rapid iterations, with nightly builds continuing to serve as the daily build verification.

V. Community, Events, and Official Homepage

5.1 The 6th RISC-V China Summit Opens in Shenzhen on 10-18; RuyiSDK Hosts Booth D15 and Gives a Talk (10-18)

Date: 2026-10-18　Source: Summit and booth announcement (community topic #2889), Biweekly Report No. 078 (topic #2891), RuyiSDK Community

The 6th RISC-V China Summit opened on 10-18 at the Shenzhen Convention and Exhibition Center (Futian) and runs through 10-20. According to the community announcement on 10-13, RuyiSDK is presenting a keynote, a poster session, and multi-solution demos at Booth D15, covering areas such as the RuyiSDK package manager, the IDE, and the development board support matrix. During the window, no new summit-related posts or recaps appeared on the forum; the latest post remains the daily news from 10-15. Talk materials and booth demo content are yet to be published after the event. What to watch: whether slides, demo solutions, and on-site feedback are added after the event.

5.2 Official Website and Intelligence Repository: No Changes to the Three Official Homepage Pages; Intelligence Repository Publishes Three Consecutive Issues (10-16 to 10-18)

Date: 2026-10-18　Source: RuyiAI official homepage, Blog page, Docs page, ruyiai-daily 10-18 issue, Site repository PR #80

The three official homepage pages showed no changes during the window: the homepage index has 3 entries, the blog has 2 posts (“RISC-V Adaptation of Triton” and “PyTorch RISC-V CI in Practice”), and the docs have 23 chapters. The technical intelligence repository ruyiai-daily published three consecutive issues on 10-16, 10-17, and 10-18. Its RISC-V section covered the runtime libcall proposal for RISC-V multiplication, the Sail RISC-V 0.16 release, the Zvabd encoding update in Unified DB, the execute-only page permission patch for linux-riscv, the KVM IMSIC locking design, and RoPE emulation for XiangShan AME, among other items. The site repository had 5 commits during the window, including a contributor guide update (PR #80) and an automatic refresh of contributors.json.

5.3 Forum and External News: No New Forum Posts; Zero Hits for Targeted Google News Queries (10-16 to 10-18)

Date: 2026-10-18 (status)　Source: RuyiSDK Community Forum, openRuyi distribution news page, arXiv RISC-V search

There were no new topics on the RuyiSDK forum during the window; the latest is still the daily news post from 10-15 (#2892), while Biweekly Report No. 078 and the summit announcement remain in place. On the external news side, Google News queries in both Chinese and English for RuyiSDK, RuyiAI, and openRuyi all returned zero hits (the channel was working normally); the only hit for “Ruyi Community RISC-V” was a container ecosystem item about the ArtCraft Ruyi Linglong edition being listed, which is unrelated to this topic. Media coverage of the RISC-V China Summit during the same period focused on industry and capital perspectives (Securities Times on 10-17, East Money on 10-16, Sina Finance on 10-18) and did not cover specific RuyiSDK content. The latest RISC-V preprint on arXiv is dated 10-15, with no new entries during the window. The openRuyi distribution news page has no new articles; the 2026.09 release announcement remains the latest.

VI. Trend Observations

6.1 Compiler stack version coupling tightens: Buddy MLIR ships two releases in two days, downstream follows same day

Buddy MLIR went from 0.1.0 to 0.1.1 in roughly two days, and both changes in 0.1.1 target deliverability — server-side cross-compilation lets buddy-server run on RISC-V machines, and the model release workflow lets model artifacts ship out of CI. Downstream response is also measured in days: triton-riscv merged #87 on 10-17 to pin 0.1.0, then was bumped to the 0.1.1 nightly by automated version tracking on the morning of 10-18; tilelang-riscv folded the Buddy MLIR release CI into its own pipeline on 10-16. Version coupling around the same LLVM backend is tightening across the three repos; the thing to watch is whether a unified release window and regression baseline emerge.

6.2 The two fork maintenance lines keep diverging: PyTorch merges and replays in parallel, LLVM silent for six days

The PyTorch riscv branch merged 143 commits in the window (mostly upstream syncs) and maintained its local patch stack via bulk replay, while also seeing its first PR merge in nearly five weeks (#51, riscv64 local image); the LLVM riscv branch, by contrast, has had no commits for six days since 10-12, with two FPGA backend PRs stalled at 10-12. Both are “upstream fork + local patch stack,” but one is a daily-moving pipeline and the other a static branch awaiting review — the gap in maintenance investment is more pronounced than in the previous window. Watch: whether the LLVM replay restarts on a new upstream baseline, and whether the FPGA backend PRs enter review.

6.3 RuyiSDK advances on three fronts: kernel probing filled in, distro coverage expanded, toolchain awaiting version window

On the kernel side, RVA23-related atomicity and instruction-fetch atomicity profile extensions were merged into cpufeature and hwprobe, with private extension IDs aligned to upstream; on the distro side, six Rust embedded packages were added, bringing the base dependencies for Rust bare-metal development into the software source; on the toolchain side, 0.54.0 is slated for late October, with ABI compatibility checks and K1/K3 adaptation continuing; the firmware line paused after three consecutive releases. The overall rhythm is “kernel probing filled in, distro coverage expanded, toolchain awaiting version window”; next, watch whether 0.54.0 ships on schedule and how the post-summit plans land.

Source Verification Table

Source Verification Result
RuyiAI-Stack org (all repos) pytorch: 143 commits on the riscv branch in the window (mostly upstream merges) + 24 local patch-stack replays + PR #51 merged + 7 open PRs with baseline refreshed, main upstream sync as usual; llvm-project: no commits on the riscv branch for six days, two FPGA PRs stalled at 10-12; triton-riscv: 2 commits (#87, #88); tilelang-riscv: 5 commits; ruyiai-daily: 3 issues; site repo: 5 commits; no pushes to harness, skills, caffe, mxnet, pytorch-ci, FBGEMM, cpuinfo, VecIntrinBench, IntrinTrans, torq-tile, dsh-osc
ruyisdk org (all repos) linux-xuantie-kernel: 4 commits (cpufeature/hwprobe and hwcap ID alignment); support-matrix: 2 commits (Zephyr and RT-Thread Smart reports for Milk-V Duo S); ruyisdk-vscode-extension: 3 commits; ruyi-imager: 1 nightly build; no in-window commits to ruyi, packages-index, ruyi-tuner, ruyici, website, wechat-articles, AME-operator, board-docs, etc.
openRuyi-Project org (all repos) openRuyi main repo: 6 commits (Rust RISC-V embedded packages); no in-window commits to ruyifirmware, edk2-ruyi, coreboot, opensbi, linux’s ruyi/7.3.y, MultiArchUefiPkg, kernel-team-tools; firmware line stopped updating after the 10-15 release
buddy-compiler org buddy-mlir main branch: 1 commit (#925) + 3 releases (0.1.1 stable and two nightlies); no commits to buddy-examples, compiler-eval
RuyiSDK community forum Zero new topics in the window; latest is #2892 (10-15 daily news); biweekly report 078 and summit announcement remain
openRuyi news page No new articles (the 2026.09 release announcement is still the latest; the 2026.10 page is not yet live)
ruyi package manager / PyPI 0.53.0 remains latest (09-24); no new version in the window
Official homepage (ruyiai.org) Three pages unchanged: homepage 3 items, blog 2 posts, docs 23 chapters
Tech intelligence repo (ruyiai-daily) Three consecutive issues on 10-16, 10-17, 10-18; the RISC-V sections cover the libcall proposal, Sail 0.16, and the execute-only page permission patch, respectively
arXiv (RISC-V) Latest entries stop at 10-15; no new papers in the window
Google News RSS (multiple Chinese and English queries) Zero hits for RuyiSDK / RuyiAI / openRuyi; one irrelevant hit for the Ruyi community query; summit coverage takes an industrial-capital angle

Full Source List