Research window: 2026-11-16 04:30 ~ 2026-11-17 04:30 (Beijing time, past 24 hours; contiguous with the cutoff of the previous 11-16 report).

Sources: GitHub key repository and organization push verification (RuyiAI-Stack 19 repos, ruyisdk 52 repos, buddy-compiler 8 repos, openRuyi-Project 49 repos, with per-repo checks of commits, PRs, and Releases within the window), triton-riscv stable and nightly asset lists, tilelang-riscv merged PR diffs, openRuyi packaging repo SPECS and kernel patchset tags, ruyisdk board documentation and ruyi-imager commits, RuyiSDK developer community forum, three-page snapshot of the official RuyiAI homepage, openRuyi distribution news page, Google News RSS targeted Chinese and English queries (via proxy), arXiv search.


This Issue’s Index

  • Today’s Focus: tilelang-riscv merges #6, RISC-V backend defaults to buddy-opt (11-16)
  • Today’s Focus: triton and buddy touch the toolchain on the same day, LLVM decoupled and dump() restored (11-16)
  • I. RuyiAI Stack Progress (PyTorch / Triton / TileLang RISC-V adaptation)
    • 1.1 pytorch riscv branch: no new PRs in the window, branch fully rebased every early morning (11-17 status)
    • 1.2 triton-riscv weekly official build: -O3 and +zvfbfmin enter the riscv64 wheels (11-16)
    • 1.3 llvm-project, pytorch-ci, FBGEMM and other key repos quiet (11-17 status)
  • II. RuyiSDK Toolchain and Distributions
    • 2.1 openRuyi backports Zvk AES to Go 1.27 (11-16)
    • 2.2 linux and linux-lts refresh patchset and config in the same minute (11-16)
    • 2.3 Three miscellaneous packaging repo commits: maturin dependency fix, mupdf workaround removal, rpm-config macro fix (11-16)
    • 2.4 ruyi-imager follows Gradle Wrapper Neo 0.4.0 (11-17)
    • 2.5 board-docs adds Jupiter2 ONNXRuntime Chinese documentation (11-16)
    • 2.6 ruyi and packages-index have zero commits, 0.54.0 remains the latest official release (11-17 status)
  • III. Vector Extensions and Operator Optimization
    • 3.1 +zvfbfmin becomes mandatory in the default feature string (11-16)
    • 3.2 VecIntrinBench, IntrinTrans and FBGEMM still quiet (11-17 status)
  • IV. Buddy Compiler Updates
    • 4.1 Mainline quiet for a day after 0.1.4, PR #1059 still open (11-17 status)
    • 4.2 Four items under review on the model side: DeepSeek tokenizer, PaddleOCR-VL, w8a8 quantization, upsample (11-17 status)
  • V. Community, Events and Official Homepage
    • 5.1 Two forum posts: xv6-riscv course part three preview, Purism phone repost (11-16)
    • 5.2 Three official homepage pages unchanged, official site repo only has bot updates to contributors file (11-17 status)
    • 5.3 ruyiai-daily gap reaches day nine (11-17 status)
    • 5.4 External news and arXiv: zero hits (11-17 status)
  • VI. Trend Observations
    • 6.1 Toolchain boundaries redrawn: one LLVM no longer covers everything
    • 6.2 Compiler choice becomes a build dimension
    • 6.3 Distributions begin adopting RISC-V-specific extensions
    • 6.4 Daily information surface continues to idle

Today’s Focus: tilelang-riscv merges #6, RISC-V backend defaults to buddy-opt (11-16)

Date: 2026-11-16 Source: PR #6, merge commit 2204c7e

On 11-16 at 14:56, tilelang-riscv merged #6 “RISC-V backend defaults to buddy-opt, with two examples added for BOSC and GEMM”. 22 files, +835 −284, two commits: the 11-04 “select buddy-opt as default and split the two toolchain roots”, and the 11-13 “add examples, update docs”. This is the repo’s first change since #5 merged on 11-03, and the repo still has only the main branch.

The structural change is in toolchain.py (+62 −4): Buddy and LLVM each have their own independent toolchain root directory, TILELANG_RISCV_OPT can explicitly override the optimizer, and the optimizer choice is written into the RISC-V compilation cache key (kernel_cache.py +4). This is more practical than the surface-level “swap the default value” — previously there was still a risk of hitting stale cached artifacts after switching optimizers; now the cache key carries the optimizer, effectively turning “which toolchain is used” into a searchable build dimension.

Two kinds of examples were added: examples/riscv/gemm is a host-side FP16 GEMM (gemm.py +47), and examples/riscv/bosc is a standalone-buildable BOSC INT8 GEMM firmware (build.py +190, launch.c +122, env.sh and README). The largest documentation change is docs/get_started/BuildOnSG2044.md (+55 −178), rewritten from step-by-step manual operations to portable paths and streamlined usage. Three test files were also added: toolchain tests +126 lines, compilation cache tests +29 lines, and adaptation pipeline tests +45 lines, all under the testing/python/riscv directory.

Today’s Focus: triton and buddy touch the toolchain on the same day—LLVM decoupled and dump() restored (11-16)

Date: 2026-11-16 Sources: triton-riscv PR #123, buddy-mlir PR #1062, triton-riscv PR #115

At 18:14 on 11-16, triton-riscv opened #123, “Decouple the backend toolchain from Triton’s LLVM.” The problem is stated in the description: the CPU backend adds no C++ to libtriton.so, and all passes go through the out-of-process triton-shared-opt, but add_triton_plugin still links the MLIR libraries and their LLVM chain into libtriton.so, so the backend toolchain can only use the one LLVM that Triton itself was compiled with. The fix is to turn off TRITON_SHARED_BUILD_CPU_BACKEND and add llvm-hash.txt to pin the LLVM package separately: libtriton.so uses the LLVM matching the Triton source, triton-shared-opt is built with Triton, and buddy-opt/buddy-translate/buddy-llc/opt/llvm-objdump come from the buddy release, exchanging only textual IR with each other. RISC-V’s +v and +xsmtime are needed only by llc, so the LLVM that Triton depends on no longer has to carry RISC-V patches. Three files, +16 −2; llvm-hash.txt is temporarily pinned to nightly/v0.1.4.dev20261103, and apart from libtriton.so having one fewer plugin, the build artifacts are unchanged.

Later in the same window (11-17 01:23), buddy-mlir opened #1062, “Build LLVM with dump() support.” The LLVM package is built with -DLLVM_ENABLE_ASSERTIONS=OFF, while MLIR/LLVM’s dump() is defined only when assertions are enabled or LLVM_ENABLE_DUMP is set, so any downstream call fails to link. The PR provides evidence: mlir::Operation::dump() is present in the nightly/v0.1.4.dev20261103 package but has disappeared from the nightly/v0.1.4.dev20261113 package. Triton is exactly such a downstream: with NDEBUG on, the header does not even declare it, and with it off, it fails to link. The patch adds just one line, LLVM_ENABLE_DUMP=ON, preserving the Release build.

Both issues point to the same place: buddy’s LLVM package is already triton-riscv’s default upstream, and a single nightly package swap can block downstream compilation. Renovate’s #115 happens to pin the dependency to nightly/v0.1.4.dev20261113 (still being updated at 21:40 on 11-16); if #1062 does not land, that pin will keep causing trouble.


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

1.1 pytorch riscv branch: no new PRs in window, branch fully rebased every early morning (11-17 status)

Date: 2026-11-17 Source: riscv branch commit list, PR list

There were no new commits on this branch in the window; the most recent is still #57 “remove JENKINS_RC”, authored 11-13 09:04, committed 11-15 19:00 UTC, i.e. Beijing time 11-16 03:00, an hour and a half before the start of this window. On the Atom single page of twenty commits, all committer timestamps are crammed into the two seconds from 11-15 19:00:25 to 19:00:26, while author timestamps span August through November (#44 is 09-08, #51 is 10-16, #57 is 11-13).

This indicates the branch is fully rebased once every early morning by a sync bot: the rebase recorded in the previous report occurred on 11-14, and today’s is the same mechanism on the following day, not twenty-six new pieces of work. The 8 open PRs (#48 RVV CPU capability detection, #46 ATen RVV support, #43 reworked patch per upstream review comments, #55 matrix_exp non-finite value counting) all show an update time of 11-16 08:30, likewise the result of rebase timestamp refreshes. Incremental progress can only be judged by PR merge time, not commit time. The main branch had another 20 commits in the window, all upstream PyTorch sync traffic (CI scripts, CUDA and LinAlg acceleration), unrelated to RISC-V.

1.2 triton-riscv weekly official release: -O3 and +zvfbfmin land in riscv64 wheel (11-16)

Date: 2026-11-16 Source: official release/20261115-e99c326, commit e99c326

At 11-16 07:39, triton-riscv published release/20261115-e99c326, marked as non-prerelease. Two wheels: riscv64 uses the manylinux_2_39 baseline, 525,973,319 bytes (about 502 MiB); x86_64 uses the manylinux_2_27/2_28 baseline, 508,635,619 bytes (about 485 MiB). The version string is triton-3.9.0+gitbbe38e57, stable ABI (abi3) from CPython 3.12.

The tag points to e99c326 from 11-14, i.e. the #117 commit: explicit targets and the cross-compilation path run opt -O3 and llc -O3, and the default llc feature string adds +zvfbfmin. Official releases ship weekly; the previous one was release/20261108-6895885 at 11-09 06:59; there was no new nightly build on the night of 11-15, so this official release occupies the nightly’s slot. The release notes are empty, so the content can only be determined by going back to the commit the tag points to.

1.3 llvm-project, pytorch-ci, FBGEMM and other key repos silent (11-17 status)

Date: 2026-11-17 Source: llvm-project (RuyiAI fork), VecIntrinBench, IntrinTrans

The llvm-project fork is stalled at 11-02, pytorch-ci at 11-12, harness at 10-27, dsh-osc at 09-15, FBGEMM at 07-13, IntrinTrans at 06-25, cpuinfo at 05-20, VecIntrinBench at 02-13, torq-tile at 04-09 — all with zero commits in the window. Only four repos in the RuyiAI-Stack organization had pushes this window: pytorch (upstream sync on the main branch), tilelang-riscv, triton-riscv and the website repo.

II. RuyiSDK Toolchain and Distributions

2.1 openRuyi Backports Zvk AES to Go 1.27 (11-16)

Date: 2026-11-16 Source: Commit 6592b995

At 14:21 on 11-16, the packaging repo landed SPECS: go: Backport SHA-2 AES optimization, adding the patch 1005-release-branch.go1.27-crypto-internal-fips140-aes-bl.patch (468 lines), with two lines added to go.spec in tandem. The description is straightforward: backport Zvk-based AES support from Go master to the 1.27 release branch; submitted by Julian Zhu.

Zvk is RISC-V’s vector crypto extension family. The patch fills in the FIPS-140 AES block routines under crypto/internal, allowing AES on riscv64 to use vector instructions rather than a purely scalar implementation; whether it is enabled depends on runtime detection of Zvk, and cores without the extension still take the original path. Last week the packaging repo had just bumped Go to 1.27.4 and filled in thirty-odd Go packages; this commit adds performance after the version settled, the second layer of “adapt first, optimize next.”

2.2 linux and linux-lts Refresh Patchset and Config in the Same Minute (11-16)

Date: 2026-11-16 Source: linux-lts commit 33a1ed14, linux commit ff744f31, kernel-team-tools tags

At 14:34 on 11-16, two commits landed in the same minute: SPECS: linux-lts: refresh patchset & refresh config and the identically named linux version. The linux-lts commit has 3 insertions and 3 deletions, only swapping the patchset and config references; the version baseline is unchanged, still linux 7.3.4 and linux-lts 6.18.63.

The kernel toolchain repo’s tags that day had already reached v7.3.4-6.1 and v6.18.63-7.1 (11-16 01:24); the previous report recorded the first releases -6 and -7. Within a single day the revision digit after the major version went from absent to present, indicating the kernel side is moving in small, fast steps: release the full tag first, then a revision tag, with the packaging repo following up with a refresh. The division of labor across the three parties in this chain is now clear—kernel-team-tools manages patchset and config versions, openRuyi manages SPECS references, and the image side only honors the final patchset_release.

2.3 Three Miscellaneous Commits in the Packaging Repo: maturin Dependency Fix, mupdf Workaround Removal, rpm-config Macro Fix (11-16)

Date: 2026-11-16 Source: python-maturin 9d1e409e, mupdf 3d32c749, rpm-config e2baa296

Three small changes also landed the same day. python-maturin (17:44, 2 insertions, 1 deletion) adds the missing unicode-xid build dependency, which previously caused failures in a clean build environment due to the missing crate. mupdf (14:54, 1 insertion, 6 deletions) removes the entire python clang workaround—import clang.cindex now works directly without presetting environment variables.

rpm-config-openruyi (11:15, 16 lines) fixes the scoping of toolchain macros: the version-suffix macro was previously unrelated to the toolchain family, so setting a version number for one toolchain would also rename another toolchain’s commands—for example, specifying major version 23 for clang would expand the GCC command set to gcc-23. The fix makes the toolchain family a macro parameter, generating suffixes only for the selected family; the commit is marked Fixes 939eeb124. Such macro errors do not blow up immediately; they only surface when a package uses both toolchains at once.

2.4 ruyi-imager Follows Gradle Wrapper Neo 0.4.0 (11-17)

Date: 2026-11-17 Source: Commit 736c5219

At 00:21 on 11-17, ruyi-imager updated Gradle Wrapper Neo to 0.4.0, touching four files: the version catalog under gradle/, the wrapper’s own Java source, and the two launch scripts (gradlew and gradlew.ps1)—the wrapper itself and the two launch scripts were swapped in the same batch. The two commits in the previous report (pausing downloads and full-image progress #22, Gradle wrapper 9.9.1) were merged on 11-15 and 11-13; this commit is a build-tool follow-up.

2.5 board-docs Adds Chinese ONNXRuntime Documentation for Jupiter2 (11-16)

Date: 2026-11-16 Source: PR #57

At 14:05 on 11-16, ruyisdk/board-docs merged #57 “Add Chinese README for ONNXRuntime setup,” adding only one file, Jupiter2/onnxruntime/README_zh.md, 370 lines. Board documentation had previously focused on image flashing, system boot, and peripherals; this piece brings inference framework deployment into scope. For developers wanting to run ONNX models on RISC-V boards, this is the first written Chinese step-by-step guide.

2.6 ruyi and packages-index See Zero Commits; 0.54.0 Remains the Latest Stable Release (11-17 Status)

Date: 2026-11-17 Source: ruyi releases, packages-index commit list

The ruyi package manager’s last commit is still 11-02, and the latest stable release is still 0.54.0, published 11-10; packages-index is likewise stalled at 11-02, with no new entries in the package index this week. The distribution news page has no new articles either—the latest are still the two from 10-19 (Ruyi Firmware and the openRuyi-Project overview)—and the 2026.11 monthly release has not yet shipped.

III. Vector Extensions and Operator Optimization

3.1 +zvfbfmin Becomes a Necessity in the Default Feature String (11-16)

Date: 2026-11-16 Source: PR #117

Three boundaries in #117’s description are worth recording. First, without Zvfbfmin, LLVM does not lower even load and convert for scalable bf16 vectors, and llc directly reports Scalarization of scalable vectors is not supported. Second, buddy-mlir’s lower-vir-to-vector preserves scalable bf16 vectors and assumes by default that the target has Zvfbfmin, so without this extension downstream fails wholesale at the llc stage. Third, once added, conversions go through vfwcvtbf16.f.f.v and vfncvtbf16.f.f.w, delegating the widening/narrowing conversions between bf16 and fp32 to the vector unit.

The RVV targets the project supports (SpacemiT K3, SOPHGO SG2044) all carry this extension; cores without it can override the default feature string via TRITON_RISCV_LLC_FEATURES. DEFAULT_MARCH is untouched because it only drives the GCC link step, and GNU as 2.42 does not recognize zvfbfmin—objects compiled with +zvfbfmin still link fine.

3.2 VecIntrinBench, IntrinTrans, and FBGEMM Remain Silent (11-17 Status)

Date: 2026-11-17 Source: VecIntrinBench, IntrinTrans, FBGEMM (RuyiAI fork)

None of the three repos saw commits within the window: VecIntrinBench is stalled at 02-13, IntrinTrans at 06-25, and FBGEMM at 07-13. The vector intrinsic benchmark and conversion toolchain have not moved in three quarters; performance data at this layer can currently only be read indirectly from triton-riscv’s operator tests and buddy’s VIR tests.

IV. Buddy Compiler Updates

4.1 Mainline Silent for a Day After 0.1.4; PR #1059 Still Open (11-17 Status)

Date: 2026-11-17 Source: Mainline commit list, PR #1059, releases

After 0.1.4 was released at 08:01 on 11-15, the mainline has no new commits; the last is still #1058 from 06:44 on 11-12. There are no new nightly packages either—the latest is nightly/v0.1.4.dev20261113. PR #1059 (replacing memref copies with vector moves, cutting the sample from 66 ms to 2.8 ms) has not been updated since 11-13 and remains open.

4.2 Four Model-Side PRs Under Review: DeepSeek Tokenizer, PaddleOCR-VL, w8a8 Quantization, upsample (11-17 Status)

Date: 2026-11-17 Source: PR #1061, PR #833, PR #945, PR #993

The mainline is idle, but the review queue keeps growing: #1061, newly opened at 09:51 on 11-16, “splits DeepSeek’s tokenizer from its chat template”; #833 from 11-14 adds PaddleOCR-VL-0.9B vision-language model integration; #945 from 11-13 implements per-token dynamic activation quantization for w8a8 MatMul; #993 from 11-12 adds tile.upsample_nearest and recognition patterns. Counting #1062, buddy-mlir currently has 10 open PRs, forming a complete review queue from model frontend through quantization to the VIR middle end.

V. Community, Events, and Official Homepage

5.1 Two Forum Posts: xv6-riscv Course Part 3 Preview, Purism Phone Repost (11-16)

Date: 2026-11-16 Source: xv6-riscv course post, Purism repost

The RuyiSDK forum had two new posts on 11-16. The 20:28 post, “Step by Step: Learning to Develop xv6-riscv” Part 3 preview, covers the file system and links in its body to the course preview on Bilibili; the 12:49 repost introduces Purism’s Librem 5 v2, based on the SpacemiT K1 octa-core processor and running PureOS, with shipments planned for April 2028. Both posts currently have only the first floor, with 4 and 5 views respectively.

5.2 Official Homepage’s Three Pages Unchanged; Official Site Repo Only Has a Bot Updating the Contributors File (11-17 status)

Date: 2026-11-17 Source: RuyiAI official homepage, blog page, official site repo

The hashes of the official homepage’s three pages match the previous check: index.html at 7246 bytes, blog.html at 5632 bytes, docs.html at 10843 bytes; the blog still has 2 posts (Triton’s RISC-V port, PyTorch RISC-V CI practices), and the docs have 23 chapters. The official site repo had a bot commit at 04:49 on 11-16 that only updated contributors.json (with skip ci) and touched no page content.

5.3 ruyiai-daily Gap Reaches Day Nine (11-17 status)

Date: 2026-11-17 Source: ruyiai-daily commit list

The daily report repo’s latest entry is still 11-08 (committed 11-08 06:21); nine issues from 11-09 through 11-17 were not generated. The gap now exceeds the eight days recorded in the previous report, and this repo currently cannot be used as a source.

5.4 External News and arXiv: Zero Hits (11-17 status)

Date: 2026-11-17 Source: arXiv cs.AR latest, openRuyi news page

Six groups of Chinese and English queries (RuyiAI, RuyiSDK, openRuyi, Ruyi community RISC-V, RuyiAI RISC-V, Ruyi RISC-V AI) all returned zero hits within the window. arXiv also had no new papers; the most recent RISC-V-related items remain the 11-12 SPEC CPU2026 analysis and the 11-02 paper on silent degradation of bf16/fp16 auto-vectorization under LLVM. All content in this issue therefore comes from code repos and the forum.

VI. Trend Observations

6.1 Toolchain Boundaries Redrawn: One LLVM No Longer Covers Everything

triton-riscv #123 and buddy-mlir #1062 are two sides of the same day. The former pulls the backend toolchain out of libtriton.so and pins LLVM separately via llvm-hash.txt; the latter restores the dump() that had been disabled by LLVM_ENABLE_ASSERTIONS=OFF. Together they show that the RuyiAI line no longer assumes “one LLVM rules all”: Triton ships its own copy, the buddy distribution has one, and the backend llc has one, each handling its own segment, with interfaces converging on textual IR.

6.2 Compiler Choice Becomes a Build Dimension

tilelang-riscv #6 makes buddy-opt the default while also writing the optimizer into the cache key. This matters more than “changing a default”: once the optimizer enters the cache key, artifacts of the same kernel under different toolchains will not contaminate each other, and switching toolchains goes from “tweaking environment variables by trial and error” to “an explicit build parameter.” Adding BOSC and GEMM examples effectively gives this path two reproducible acceptance points.

6.3 Distributions Begin to Absorb RISC-V-Specific Extensions

openRuyi’s activity this week centered on extensions: Go backfills Zvk AES, the triton wheel ships with +zvfbfmin by default, and the kernel patchset and config were refreshed twice in one day. None of these are parts that generic upstream can cover automatically; they must be filled in item by item by distribution and toolchain maintainers. After RVA23, the differentiation is shifting from “whether it runs” to “whether the vector and crypto extensions are usable.”

6.4 The Daily Information Surface Keeps Idling

The official homepage is static, ruyiai-daily is on day nine of its gap, and external news has zero hits; all material in this issue comes from commits and PRs across four GitHub organizations plus two forum posts. In this state, the report’s judgment value depends mainly on understanding the commit contents rather than the number of news items—especially for the triton release with empty release notes, where one can only go back to the commits the tag points to.

Appendix

Source Verification Table

Source Verification Result
RuyiAI-Stack (19 repos) tilelang-riscv merged 1 PR, triton-riscv shipped 1 official release and opened 1 new PR, pytorch riscv branch had zero commits; all other repos quiet
ruyisdk (52 repos) ruyi-imager 1 commit, board-docs merged 1 PR; ruyi and packages-index had zero commits
buddy-compiler (8 repos) buddy-mlir main branch had zero commits, opened new PR #1062, 10 under review
openRuyi-Project (49 repos) packaging repo 6 commits, kernel tagged v7.3.4-6.1 and v6.18.63-7.1, plus 10 PRs under review
RuyiAI official site index, blog, and docs pages unchanged; 2 blog posts, 23 documentation chapters
ruyiai-daily stalled at 11-08; nine issues from 11-09 to 11-17 not generated
openRuyi distro news page no additions, latest still the two posts from 10-19; 2026.11 monthly release not published
Google News zero hits across six targeted Chinese and English query sets within the window
arXiv no new papers on RISC-V AI compilers within the window

Full Source List

Limitations

This issue’s window is 24 hours (11-16 04:30 to 11-17 04:30). On the GitHub side, anonymous API and Atom feeds were cross-checked; API quota is limited, so a few repositories were counted via Atom. The pytorch fork’s commit count is affected by daily branch rebasing, so the main text judges recency solely by PR merge time. The triton official release has no release notes attached; its contents were verified against the commit the tag points to. On the external news side, Google News was scraped via proxy, with zero hits across six query sets; we cannot rule out Chinese-language media coverage that has not been indexed.