RuyiAI Daily Intelligence Report (2026-11-18)
Research window: 2026-11-17 04:30 ~ 2026-11-18 04:30 (Beijing time, past 24 hours; directly contiguous with the cutoff of the previous 11-17 report).
Sources: GitHub push verification for key repositories and organizations (RuyiAI-Stack 18 repos, ruyisdk 29 repos, buddy-compiler 8 repos, openRuyi-Project 30 repos, with per-repo checks of commits, PRs, and Releases within the window), diffs and verification records for merged PRs in llvm-project and triton-riscv, SPECS changes in the openRuyi packaging repo, commits to the abaci-bot governance pipeline, ruyisdk extension and site repositories, the RuyiSDK developer forum, three-page snapshots of the official RuyiAI homepage, the ruyiai-daily daily-update repo, the openRuyi distribution news page, the IREE 3.14.0 release notes, the RISE Python Wheels distribution recipe, targeted Google News RSS queries in Chinese and English (via proxy), and arXiv searches.
This Issue’s Index
- Today’s Focus: LLVM fork merges XAME, ZTT v0.6 matrix backend lands 47 files in one go (11-17)
- Today’s Focus: triton-riscv fixes bf16 converter ABI, all three riscv64 CI legs green on real hardware for the first time (11-17)
- I. RuyiAI Stack Progress (PyTorch / Triton / TileLang RISC-V adaptation)
- 1.1 pytorch riscv branch sees no rebase for two consecutive nights, all twenty main commits are upstream (11-17 status)
- 1.2 triton-riscv FlagGems example PR expands to 111 files, still open (11-17)
- 1.3 llvm-project review queue down to two lines: XSAI and XBOSCAME (11-17 status)
- 1.4 tilelang-riscv zero commits, two old PRs still open (11-17 status)
- II. RuyiSDK Toolchain and Distributions
- 2.1 openRuyi introduces openssl-3 compatibility package with ten RISC-V optimization patches (11-17)
- 2.2 opensbi 1.9, mesa 26.3.0 and venus-protocol 1.1.3 land the same day (11-17)
- 2.3 json-c 0.19 triggers dnf5 build fix, nineteen commits in packaging repo in one day (11-17)
- 2.4 AI stack tracks upstream: huggingface-hub, sentence-transformers and tvm-ffi among batch of packages (11-17)
- 2.5 abaci-bot pushes twenty commits at once, ABI and CVE gating hardened (11-17)
- 2.6 RAVA_ROOTFS unifies DNS, ruyisdk extensions and site see minor updates (11-17)
- III. Vector Extensions and Operator Optimization
- 3.1 bf16 libcall family still has two spots without regression coverage (11-17 status)
- 3.2 IREE 3.14.0 adds f16/bf16 inner_tiled MMA for RISC-V V (11-16)
- 3.3 VecIntrinBench, IntrinTrans and FBGEMM remain silent (11-17 status)
- IV. Buddy Compiler Updates
- 4.1 Mainline still silent, LLVM dump() PR updated but unmerged (11-17 status)
- 4.2 Review queue continues to focus on model samples and quantization (11-17 status)
- V. Community, Events and Official Site
- 5.1 ruyiai-daily resumes after eight-issue gap, one issue covers nine days (11-17)
- 5.2 Official site’s three pages unchanged, official repo has only contributor files (11-17 status)
- 5.3 No new forum topics, one more reply on course thread (11-17)
- 5.4 Zero hits in external news, no additions to openRuyi news page (11-17 status)
- VI. Trend Observations
- 6.1 Matrix extensions begin to have compiler outlets
- 6.2 This week’s main thread is bf16
- 6.3 Distributions are preparing for ABI migration
- 6.4 Information surface keeps idling, code surface is busy
Today’s Focus: LLVM fork merges XAME, ZTT v0.6 matrix backend lands 47 files in one go (11-17)
Date: 2026-11-17 Source: PR #36, merge commit 542365c
At 15:05 on 11-17, RuyiAI’s llvm-project fork merged #36 “[RISCV][XAME] Add ZTT v0.6 matrix backend support”. The PR was opened the previous morning and completed review the next day: 47 files, +4084 −19, of which the instruction definition RISCVInstrInfoXAME.td alone accounts for 1732 lines, builtin definitions 517 lines, register info 120 lines, plus a 262-line state-handling pass. This is the fork’s mainline’s first change since it stalled on 11-02.
What was merged is a complete matrix backend path, not scattered instructions: xame as a local feature name (version 0.6) lowers the matrix and accumulator SSA values in the LLVM IR produced by MLIR down to RISC-V instructions; the llvm.riscv.ztt.* builtin names and the riscv.ztt.matrix/riscv.ztt.acc target types follow the ZTT v0.6 compiler interface and constitute a downstream implementation of the interim Attached Matrix Extension. The documentation specifies two fixed profiles: the default +xame is 8×8, 16 M registers, 8 ACCs, with a 64-bit element cap; +xame,+xame-gem5 is 4×4, 32 M, 4 ACC, 128-bit. Both count in 32-bit register units.
The bulk of the engineering effort is in registers and calling conventions: 138 shared instruction encodings, matrix and ACC register groups, CSR operands, and profile-specific assembly and disassembly; after register allocation a new state pass is added to ensure descriptors, data, and state are not clobbered during register copies and spills. Matrix parameters use a compiler-local calling convention, not the RISC-V psABI standard; both caller and callee must agree on the same profile and register types, and parameters exceeding the register file are rejected and can only go through memory. Scalar overloads are uniformly normalized to unsigned XLEN-bit types; frontends needing signed interpretation must sign-extend themselves.
Validation covers three areas: LLVM RISC-V CodeGen and MC 3381/3382 pass, all 11 XAME-specific tests pass, and the only failure is a pre-existing baseline encoding discrepancy in xboscame-valid.s (the test expects ACC encoding 8, whereas in the unmodified definitions ACC0 is 0; the BOSCAME file itself was untouched); all 10 AME conversion regressions in the external Buddy MLIR harness pass; a 4×4 integer matrix multiply (A from 1 to 16, B all ones) compiles, links, and runs in AME_gem5, with the 16 outputs being exactly the row sums 10, 26, 42, 58, and guest exit code 0.
Today’s Highlight: triton-riscv Fixes bf16 Converter ABI, riscv64’s Three CI Legs All Green on Real Hardware for the First Time (11-17)
Date: 2026-11-17 Source: PR #121, Issue #114
At 18:37 on 11-17, triton-riscv merged #121 “Fix the launcher ABI of the bf16 conversion helpers”, two files +190 −7, the bulk being the prototypes of two helpers in backend/driver.py, plus a new 166-line test. The problem lay in the register class: the launcher defined __truncsfbf2 and __extendbfsf2 with uint16_t integer prototypes, whereas the call sites generated by llc pass bf16 in floating-point registers—xmm0 on x86-64, fa0 on riscv64—with the caller taking the value from the low 16 bits; the integer return lands in eax/a0, so every kernel converting fp32 to bf16 stored the residue of the previous floating-point operation, either zero or garbage.
The fix changes the prototypes of both helpers to float, keeping the bf16 bits in the low 16 bits of the floating-point return value; __bf16 itself cannot be used because the launcher is compiled by g++, and g++ 13 on Ubuntu 24.04 does not have this type on riscv64. __truncdfbf2 and the rest of the bf16 libcall family are explicitly listed as unchanged, since the current lowering does not produce them.
The new test python/examples/test_bf16_convert.py aligns fp32 and bf16 conversions bit-for-bit against torch’s int16 view, covering the four boundary classes of round-to-nearest-even (below half, ties with even and odd lsb, above half, and float32 max to infinity), four of which failed before the fix; it then pins down the libcall path with relocation assertions—host-target builds are skipped on x86 with avx512bf16 (where llc lowers bf16 natively and does not go through the helper), while riscv64 builds strip +zvfbfmin to force conversions through the launcher, incidentally serving as a probe of the bare runtime path.
The verification results are worth recording: on x86 host, the reproducer kernel from #114 returns [-5.0, -0.5, 2.5, 7.0] after the fix, versus all zeros before; the host example suite passes 4028 with 14 skipped, and the 10 failures are pre-existing failures in test_affine_grid_generator and test_avg_pool3d (they fail identically with the fix stashed, and neither case uses bfloat16); all three riscv64 CI legs (three Python versions) pass the full suite—the first time this fix has been verified on real riscv64. After merging with the FlagGems branch from #120, all 41 bf16 xfail pins turned into passes, with 461 cases passing.
I. RuyiAI Stack Progress (PyTorch / Triton / TileLang RISC-V Porting)
1.1 pytorch riscv branch has not been rebased for two consecutive nights; all twenty main commits are upstream (11-17 status)
Date: 2026-11-17 Source: riscv branch commit list, PR list
The fork’s default branch is riscv, and the latest commit is still #57 “remove JENKINS_RC”, landed at 03:00 (Beijing time) on 11-16 with an author date of 11-13. The nightly whole-branch rebase that previously occurred once per night did not appear on either the night of 11-16 or 11-17; the previous report recorded it as “rebased once every night around midnight,” but based on the current state it should be revised to “rebase has stopped for two nights,” and increments should no longer be inferred from the clock. The 8 open PRs last updated at 11-16 08:30, which is likewise the timestamp-refreshing behavior of a rebase and should not be treated as new activity.
All 20 commits on the main branch within the window are upstream PyTorch sync traffic: MPS upsample forward moved onto the plane grid, ROCm’s MaybeSetDevice fallback, Inductor filtering Blackwell’s transposed FP32 config, DCP’s FsspecReader batching and async prefetch, TritonPrinter’s float64 literal fix, etc. — none related to RISC-V.
1.2 triton-riscv’s FlagGems examples PR has grown to 111 files, still open (11-17)
Date: 2026-11-17 Source: PR #120, PR #123
#120 “Add FlagGems operator examples (batches 1-6)” is currently the largest open item: 111 files, +8592 −4, still being updated at 11-17 20:59. It moves FlagGems operator examples into triton-riscv’s examples directory in batches, effectively equipping the RISC-V backend with a validation suite drawn from the upstream operator library; the 41 bf16 xfails promoted to passing in #121 were run off this branch.
#123 “Decouple the backend toolchain from Triton’s LLVM” has not been updated since it was opened on 11-16; it remains three files, +16 −2, with llvm-hash.txt still pinned to nightly/v0.1.4.dev20261103. The repo currently has 19 open PRs.
1.3 llvm-project’s open queue still has the XSAI and XBOSCAME lines (11-17 status)
Date: 2026-11-17 Source: PR #33, PR #28
After XAME was merged, two older PRs remain open in the fork: #33 “Add XSAI ZAMES and ZMASYNC vendor extensions”, opened 10-26 and last updated 11-05; and #28 “Feat/xboscame fpga”, opened 09-23 and updated 11-02. Both are vendor extension lines that coexist with the just-merged XAME — BOSCAME’s existing encoding definitions were untouched this time, and the description in #36 specifically explains that the xboscame-valid.s failure is a baseline difference. The same fork carries three vendor extension lines in parallel — XBOSCAME, XAME, and XSAI — without overriding one another.
1.4 tilelang-riscv has zero commits, two old PRs still open (11-17 status)
Date: 2026-11-17 Source: commit list, PR #4, PR #2
The repo is parked at the merge commit from 11-16 14:56, with zero commits in the window. Neither open item has moved: #4 “Add RVV vector mask and max reduction lowering” was opened 9-28 and has not been updated since that day; #2 “Add Codex-compatible RISC-V operator workflow” was opened 6-08. The #6 merged in the previous issue set buddy-opt as the default and wrote the optimizer into the cache key; there has been no further progress this week.
II. RuyiSDK Toolchain and Distributions
2.1 openRuyi Introduces openssl-3 Compatibility Package with Ten RISC-V Optimization Patches (11-17)
Date: 2026-11-17 Source: Commit 9f1c8f64, openRuyi packaging repo
At 16:13 on 11-17, the packaging repo added SPECS/openssl-3, version 3.6.5, with 11 files and +5603 lines. The commit message is blunt: openssl 4.x has ABI changes, so following the practice of other distributions, an openssl-3 compatibility package is provided first; it will conflict with the current openssl 3.x, and installation failure is expected. The main openssl.spec in the repo still says 3.6.5, meaning this is a paving-the-way move—the compatibility package is in place first, so downstream has a fallback when the main package switches to 4.x.
The ten patches brought in are all RISC-V vector and assembly optimizations: a hand-written assembly implementation of ChaCha20 (686 lines), GHASH multi-block aggregation (997 lines), GHASH Zvbc multi-block aggregation (615 lines), GHASH Zvkg multi-block aggregation (255 lines), SHA256 instruction reordering (66 lines), an AES-XTS comment fix (44 lines), an SM4-CBC implementation (883 lines), an AES-128-CBC decryption improvement (456 lines), SM2 generic riscv64 assembly (1360 lines), plus a shared jitterentropy patch. Cryptographic libraries are starting to take advantage of vector crypto extensions like Zvbc and Zvkg on RISC-V, the same thread as last week’s Go backfill of Zvk AES.
2.2 opensbi 1.9, mesa 26.3.0 and venus-protocol 1.1.3 Land on the Same Day (11-17)
Date: 2026-11-17 Source: opensbi commit bfb0f385, mesa commit 1df086dd, venus-protocol commit a44cfb84
At 20:40, opensbi was upgraded from 1.8 to 1.9, with sbi_fp.h and sbi_pmp.h added to the header list—the only explicit interface change this time. The two commits at 14:26 are graphics stack: mesa was upgraded to 26.3.0, the 26.2.4 PVR fallback patch was removed, and the PVR conformance and zink KMSRO patches were rebased onto the new baseline; at the same time venus-protocol 1.1.3 was added—the protocol definitions and generated headers for passing Vulkan commands over Virtio-GPU, noarch, meson build. With Venus in the distribution, Vulkan in a RISC-V VM can be passed through from the host without waiting for an on-board GPU driver.
2.3 json-c 0.19 Triggers a dnf5 Build Fix; Nineteen Commits in the Packaging Repo in One Day (11-17)
Date: 2026-11-17 Source: json-c commit 5ebafccb, dnf5 commit ba5d7e88
At 10:32, json-c was upgraded from 0.18 to 0.19: the old workaround for the cmake policy version floor was removed, and the xxd build dependency was added. A later commit at 16:13 fixes dnf5—in 0.19’s linkhash.h, lh_get_hash is defined as a static inline but never used, and -Werror judges it a build failure outright; the fix adds -Wno-error=unused-function for that section, with the original error pasted in the comment.
The packaging repo had 19 commits that day: besides the three above, there were krb5 1.22.3, mock 6.9, python-pyside6 switching llvm22-static to llvm-static, openruyi-desktop-setup-kde adding requires, CI builds switching to openssl, and the batch of Python packages in section 2.4.
2.4 AI Stack Follows Upstream: huggingface-hub, sentence-transformers, tvm-ffi and More (11-17)
Date: 2026-11-17 Source: packaging repo commit list
Among the eight commits pushed in the same second at 15:03, those directly related to the AI stack are: huggingface-hub 1.32.0, sentence-transformers 6.3.0 (commit tagged security-fixes), apache-tvm-ffi 0.1.12, xgrammar 0.2.9 (also tagged security-fixes), hf-xet 1.5.2, plus click 8.5.1 and two rust-tokio-with-wasm 0.8 packages. tvm-ffi is TVM’s FFI layer, xgrammar is a grammar-constraint library for structured output, and sentence-transformers is a common front end for vector retrieval—all three sit in the RISC-V AI deployment chain, and following upstream is less work than one-off porting.
2.5 abaci-bot Pushes Twenty Commits at Once, Hardening ABI and CVE Gates (11-17)
Date: 2026-11-17 Source: abaci-bot commit list
At 12:30, abaci-bot under openRuyi-Project pushed 20 commits at once, all from the same author with the same timestamp, likely a backlog landing as a batch. The content centers on three gates: ABI comparison no longer relies on the system-provided abipkgdiff, supports RPM v6 payloads and xz/bzip2/lzma unpacking, treats unparseable packages as “unchecked” rather than “clean”, excludes source and debug packages, and treats abipkgdiff stderr as a failure signal; on the license side, SPDX validation and atomic writes; on the CVE side, embargo-aware cache TTL and lts/ prefix support. The container was also upgraded to Fedora 45 and publishes images following buildx’s target architectures.
The repo’s description is just an abacus emoji; from the commit messages it is a package governance pipeline: run ABI diff, license and CVE checks before commit, and block on failure. As openRuyi’s package count grows, gates like these matter more to long-term maintainability than merging one more package.
2.6 RAVA_ROOTFS Unifies DNS; Minor ruyisdk Extension and Site Updates (11-17)
Date: 2026-11-17 Source: RAVA_ROOTFS commit 35c5d945, vscode extension commit e3b9e419, ruyi-imager releases
At 18:43, RAVA_ROOTFS unified the rootfs DNS to 8.8.8.8, effective for both the img.zst and tar.gz artifacts. On the ruyisdk side, four commits: two for the vscode extension at 17:49 (removing a useless button from the news context menu and adding copy, and documenting the tools/ directory in CONTRIBUTING, by sisungo); two site cron jobs at 00:40 (api data #612, submodules #613); and a nightly ruyi-imager build at 09:55. ruyi and packages-index remain at zero commits, with 0.54.0 still the latest stable release.
openRuyi’s review queue had 10-plus updates that day, none merged: curl 8.23.0 security fixes, libjpeg-turbo 3.2.1, acpica 20260930, libspng enabling generated %check on riscv64, zchunk splitting out a tests subpackage, openruyi-test-runner as a unified test runner, and two “fix RISC-V build failure” commits. The repo currently has 63 open PRs.
III. Vector Extensions and Operator Optimization
3.1 Two Members of the bf16 libcall Family Still Lack Regression Coverage (11-17 Status)
Date: 2026-11-17 Source: PR #121
The description of #121 draws its own boundary: __truncdfbf2 and the remaining members of the bf16 libcall family are left unchanged because the current lowering does not produce them; __extendbfsf2 had its prototype changed but no tests were run — both targets inline bf16-to-f32 as shifts, with zero relocations, so the only way to confirm the argument register class is to disassemble the launcher’s .so and inspect the movss %xmm0 prologue. This means that if some future lowering degrades into a scalar libcall, no test case will catch that path.
Comparing with #117 makes this clearer: #117 puts +zvfbfmin into the default feature string, steering cores with vector extensions toward vector conversion; #121 fixes the path that falls back to libcall when that extension is absent. The semantics of the two paths must be bit-for-bit identical, yet only the vector path currently has bit-exact tests; the libcall path relies on the four boundary cases added in this round.
3.2 IREE 3.14.0 Adds f16/bf16 inner_tiled MMA for RISC-V V (11-16)
Date: 2026-11-16 Source: IREE v3.14.0
At 18:15 on 11-16, IREE released 3.14.0. The RISC-V V path of the CPU backend gains inner_tiled MMA for f16 (vfmacc, vfwmacc, Zvfhmin) and bf16 (vfwmaccbf16); math.roundeven now stays as a native instruction on riscv64 with the D extension instead of falling back to a software sequence; and one .vmfb reproducibility issue was fixed (LLVMCPU no longer writes uninitialized source location lines).
IREE follows a different MLIR downstream route, parallel to Buddy/RuyiAI’s Linalg-to-llvm-cpu path. Its addition of bf16 MMA in the same week shows that low-precision matrix multiplication has become a shared to-do item across RISC-V compiler stacks.
3.3 VecIntrinBench, IntrinTrans, and FBGEMM Remain Silent (11-17 Status)
Date: 2026-11-17 Source: VecIntrinBench, IntrinTrans, FBGEMM (RuyiAI fork)
All three repos still have no 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 been untouched for three quarters, so performance data can still only be read indirectly from triton-riscv’s operator tests and buddy’s VIR tests.
IV. Buddy Compiler Updates
4.1 Main Branch Still Silent; LLVM dump() PR Updated but Unmerged (11-17 Status)
Date: 2026-11-17 Source: Main branch commit list, PR #1062
After the 0.1.4 release, the main branch still has zero commits, with the last one being #1058 on 11-12; the nightly build is stuck at nightly/v0.1.4.dev20261113. #1062 “Build LLVM with dump() support” was updated at 16:02 on 11-17, still with a single file and +1 −0, and remains unmerged. This PR pairs with triton-riscv #123: one splits LLVM into a separate package, the other ensures the new package does not lose dump().
4.2 Review Queue Still Dominated by Model Samples and Quantization (11-17 Status)
Date: 2026-11-17 Source: PR #1061, PR #833, PR #945, PR #993, PR #1059
The review queue saw no merge activity: #1061 separates DeepSeek’s tokenizer from its chat template (+705 −100, 12 files), #833 adds the PaddleOCR-VL-0.9B vision-language model, #945 implements per-token dynamic activation quantization for w8a8 MatMul, and #993 adds tile.upsample_nearest and recognition patterns — all four remain open; the mid-end #1059 (replacing memref copies with vector transfers) is also still open. The front end is growing while the mid end waits — that has been the norm this week.
V. Community, Events, and Official Homepage
5.1 ruyiai-daily resumes after an eight-issue gap, with one issue covering nine days (11-17)
Date: 2026-11-17 Source: daily-news-2026-11-17.md, commit e1e6cffe
At 11:40, ruyiai-daily committed daily-news-2026-11-17.md, 40 KB, titled “Codex Technical Intelligence Daily (2026-11-17)”, with the in-document window written as 11-08 05:13 to 11-17 10:54, covering nine days in one go. The repo now holds 72 issues, and the eight issues from 11-09 to 11-16 are still empty—the gap noted in the previous report was not filled day by day but folded into a single long-window issue.
This issue covers PyTorch, LLVM/MLIR, Triton and TileLang, RISC-V, and the AI industry, and includes the triton 3.9.0 distribution recipe proposal for RISE Python Wheels: the source is specified as RuyiAI-Stack/triton-riscv, with plans to reuse release.sh and the Buddy/LLVM prebuilt toolchain to produce cp312-abi3 manylinux riscv64 wheels. That PR (riseproject-dev/python-wheels #4895) was opened on 11-16, still had updates at 11-18 03:22, touches two files with +222, and has not yet been merged.
5.2 Official homepage’s three pages unchanged; official site repo only has a contributors file (11-17 status)
Date: 2026-11-17 Source: RuyiAI official homepage, blog page, official site repo
The hashes of the three pages match last time: index.html 7246 bytes, blog.html 5632 bytes, docs.html 10843 bytes; the blog still has 2 posts (RISC-V adaptation of Triton, PyTorch RISC-V CI practices), and the docs have 23 chapters. The official site repo had a bot commit at 11-17 07:58 that only updated contributors.json (with skip ci) and did not touch page content.
5.3 No new forum topics; one more reply on the course thread (11-17)
Date: 2026-11-17 Source: Latest topics in the RuyiSDK community, course thread 2910
There were no new topics in the forum window; the two latest threads are still the 11-16 preview of “Step by Step: Learning to Develop xv6-riscv” Part 3 and a repost of Purism Librem 5 v2. The course thread gained one reply at 11-17 17:53, with two posts and 11 views in total; the other thread still has one post. No issue 081 of the RuyiSDK biweekly progress has appeared after issue 080 (11-11).
5.4 Zero hits in external news; no additions on the openRuyi news page (11-17 status)
Date: 2026-11-17 Source: openRuyi news page, arXiv cs.AR
All eight groups of Chinese and English queries (RuyiAI, RuyiSDK, openRuyi, Ruyi community RISC-V, Ruyi RISC-V AI, including when:2d and when:7d) returned zero hits within the window; arXiv’s RISC-V-related searches had no new entries; the openRuyi news page is still stuck on the two posts from 10-19 (Ruyi Firmware and the openRuyi-Project overview), and the 2026.11 monthly release has not yet been published. This issue’s material therefore still comes entirely from code repos, the daily repo, and the forum.
VI. Trend Observations
6.1 Matrix extensions now have a compiler outlet
The XAME change puts 138 instructions, two profiles, register scheduling, and calling conventions into LLVM in one go, and validates them with Buddy’s AME conversion and actual gem5 runs. As with last week’s RVV bf16, whether an extension is usable now depends on three things being in place at the same time: the compiler can generate it, the simulator can run it, and the operator library has a corresponding entry point. Shipping only instruction definitions without the compiler now amounts to not shipping at all on RISC-V.
6.2 This week’s main thread is bf16
#117 puts +zvfbfmin into the default feature string, #121 fixes the register class for libcalls when that extension is absent, and IREE 3.14.0 adds bf16 MMA for RISC-V V—three actions point to the same thing: bf16 on RISC-V is not one path but “vector extension goes vector, otherwise goes libcall.” The two paths must be bit-for-bit identical, and a missing link in either will show up as the hardest-to-debug symptom of all: “the result is zero.”
6.3 The distribution is preparing for an ABI migration
The openssl-3 compatibility package landed first while the main package remains at 3.6.5, with the conflict explicitly documented as expected behavior; on the same day, abaci-bot hardened ABI comparison, SPDX validation, and the CVE embargo cache. openRuyi treats “ABIs that will break in the future” as an engineering item to manage in advance rather than patching on the day of the switch. This approach determines whether a distribution can track upstream over the long term far more than merging a few extra packages.
6.4 The information side keeps idling while the code side is busy
External news had zero hits, the forum had no new topics, and the three homepage pages did not move, yet within the window two compiler mid-end changes were merged, there were 19 packaging repo commits and 20 governance bot commits. The daily report’s value for judgment continues to depend on reading commit contents rather than counting news items; when release notes are empty or missing, the only option is to go back to merge commits and test records to verify.
Appendix
Source Verification Table
| Source | Verification Result |
|---|---|
| RuyiAI-Stack (18 repos) | llvm-project merged #36 (47 files +4084), triton-riscv merged #121 (2 files +190); pytorch default branch riscv has zero commits, main’s 20 commits are all upstream; tilelang-riscv zero commits; the rest silent |
| ruyisdk (29 repos) | vscode extension 2 commits, official website 2 cron entries, ruyi-imager nightly build once; ruyi and packages-index zero commits |
| buddy-compiler (8 repos) | buddy-mlir main branch zero commits; #1062 has updates and remains open; #1059, #1061, #833, #945, #993 all under review |
| openRuyi-Project (30 repos) | packaging repo 19 commits, abaci-bot 20 commits, ceph-ci 2 commits, RAVA_ROOTFS 1 commit; openssl-3 3.6.5 new package, opensbi 1.9, mesa 26.3.0, venus-protocol 1.1.3 landed; 63 PRs under review |
| RuyiAI official homepage | index, blog, docs pages unchanged; blog 2 posts, docs 23 chapters |
| ruyiai-daily | Backfilled the 11-17 issue (covering 11-08 to 11-17); the eight issues from 11-09 to 11-16 remain missing |
| openRuyi distribution news page | No additions; latest remains the two posts from 10-19; the 2026.11 monthly release has not shipped |
| Google News | Zero hits within the window across eight sets of targeted Chinese and English queries |
| arXiv | No new RISC-V-related entries |
| IREE | v3.14.0 released on 11-16, including f16/bf16 inner_tiled MMA for RISC-V V |
| RISE Python Wheels | triton 3.9.0 distribution recipe PR #4895 still open, source points to triton-riscv |
Complete Source List
- [1] llvm-project PR #36 XAME/ZTT v0.6 matrix backend — https://github.com/RuyiAI-Stack/llvm-project/pull/36
- [2] llvm-project merge commit 542365c — https://github.com/RuyiAI-Stack/llvm-project/commit/542365c9cd3853083ceb91951322b487c520fefe
- [3] llvm-project PR #33 XSAI ZAMES/ZMASYNC under review — https://github.com/RuyiAI-Stack/llvm-project/pull/33
- [4] llvm-project PR #28 XBOSCAME FPGA under review — https://github.com/RuyiAI-Stack/llvm-project/pull/28
- [5] llvm-project fork commit list — https://github.com/RuyiAI-Stack/llvm-project/commits/main
- [6] triton-riscv PR #121 bf16 converter ABI fix — https://github.com/RuyiAI-Stack/triton-riscv/pull/121
- [7] triton-riscv merge commit e9c34b7 — https://github.com/RuyiAI-Stack/triton-riscv/commit/e9c34b711407fbd10e98a43849f7f96e32fa1946
- [8] triton-riscv issue #114 fp32 to bf16 produces incorrect results — https://github.com/RuyiAI-Stack/triton-riscv/issues/114
- [9] triton-riscv PR #120 FlagGems operator examples — https://github.com/RuyiAI-Stack/triton-riscv/pull/120
- [10] triton-riscv PR #123 decoupling toolchain from Triton’s LLVM — https://github.com/RuyiAI-Stack/triton-riscv/pull/123
- [11] triton-riscv PR #117 explicit target -O3 and default +zvfbfmin — https://github.com/RuyiAI-Stack/triton-riscv/pull/117
- [12] triton-riscv commit list — https://github.com/RuyiAI-Stack/triton-riscv/commits/main
- [13] pytorch (RuyiAI fork) riscv branch commit list — https://github.com/RuyiAI-Stack/pytorch/commits/riscv
- [14] pytorch (RuyiAI fork) PR list — https://github.com/RuyiAI-Stack/pytorch/pulls
- [15] tilelang-riscv PR #4 RVV masking and max reduction — https://github.com/RuyiAI-Stack/tilelang-riscv/pull/4
- [16] tilelang-riscv PR #2 Codex-compatible RISC-V operator workflow — https://github.com/RuyiAI-Stack/tilelang-riscv/pull/2
- [17] openRuyi commit: openssl-3 3.6.5 compatibility package — https://github.com/openRuyi-Project/openRuyi/commit/9f1c8f640ae7d6a615afe9f71bbf42bb0bc4f353
- [18] openRuyi commit: CI build switched to openssl — https://github.com/openRuyi-Project/openRuyi/commit/0b1017670fd2eef55922fc7960580ccd94491669
- [19] openRuyi commit: opensbi 1.9 — https://github.com/openRuyi-Project/openRuyi/commit/bfb0f3855039206fccb1eff41e8131a6daf54fb3
- [20] openRuyi commit: mesa 26.3.0 — https://github.com/openRuyi-Project/openRuyi/commit/1df086dd2d0dcfd98a05d5f02f5dfc26b711b3b2
- [21] openRuyi commit: venus-protocol 1.1.3 — https://github.com/openRuyi-Project/openRuyi/commit/a44cfb84c084d23b8ea43c7822bc5f35a984e454
- [22] openRuyi commit: json-c 0.19 — https://github.com/openRuyi-Project/openRuyi/commit/5ebafccbe2779fa4f86431cf4ddd9549a1e38bbd
- [23] openRuyi commit: dnf5 adapted to json-c 0.19 — https://github.com/openRuyi-Project/openRuyi/commit/ba5d7e881f279175a2434d36ab565dbb15ab379b
- [24] openRuyi commit: krb5 1.22.3 — https://github.com/openRuyi-Project/openRuyi/commit/e73dc68b818a1d4d9bb56e60879a7f9036c2cb59
- [25] openRuyi commit: mock 6.9 — https://github.com/openRuyi-Project/openRuyi/commit/894c4176e50d33a5f09b8e1a9ebbcd0646f3762b
- [26] openRuyi commit: python-pyside6 switched to llvm-static — https://github.com/openRuyi-Project/openRuyi/commit/1ed0d0600924a73835ee9cc8694796a412fe47b3
- [27] openRuyi commit: huggingface-hub 1.32.0 — https://github.com/openRuyi-Project/openRuyi/commit/31044d342d9c8f6e2c0c2f46eaaff35eb22810eb
- [28] openRuyi commit: sentence-transformers 6.3.0 — https://github.com/openRuyi-Project/openRuyi/commit/39a4585c97f92c7e0d41b0d1054adbbb79599451
- [29] openRuyi commit: apache-tvm-ffi 0.1.12 — https://github.com/openRuyi-Project/openRuyi/commit/acc9d30307d9cdc24cf11e6be609312173f8ccf7
- [30] openRuyi commit: xgrammar 0.2.9 — https://github.com/openRuyi-Project/openRuyi/commit/b12f5722f225522657eb8981995d0410186db3ba
- [31] openRuyi commit: hf-xet 1.5.2 — https://github.com/openRuyi-Project/openRuyi/commit/9117e5c79655696eb266970a9f828aa3398c4d6d
- [32] openRuyi commit: click 8.5.1 — https://github.com/openRuyi-Project/openRuyi/commit/2d9977b3bd6283081d912eace5fbf8f55ca5a72f
- [33] openRuyi packaging repo commit list — https://github.com/openRuyi-Project/openRuyi/commits/main
- [34] openRuyi packaging repo PR list under review — https://github.com/openRuyi-Project/openRuyi/pulls
- [35] abaci-bot commit list — https://github.com/openRuyi-Project/abaci-bot/commits/master
- [36] RAVA_ROOTFS commit: unified DNS — https://github.com/openRuyi-Project/RAVA_ROOTFS/commit/35c5d9455dbd3bc74e79476001828701b5882510
- [37] openRuyi distribution news page — https://openruyi.cn/zh-Hans/news/
- [38] ruyisdk-vscode-extension commit e3b9e419 — https://github.com/ruyisdk/ruyisdk-vscode-extension/commit/e3b9e41916ffeb4c7888737db204913db0401d63
- [39] ruyisdk-vscode-extension commit 25fa9866 — https://github.com/ruyisdk/ruyisdk-vscode-extension/commit/25fa986699f6865833b6e450b19f054fa42ec06b
- [40] ruyisdk-website commit c22da415 (api data) — https://github.com/ruyisdk/ruyisdk-website/commit/c22da4157f179df40891535de4157213285c3179
- [41] ruyisdk-website commit 94b0470a (submodules) — https://github.com/ruyisdk/ruyisdk-website/commit/94b0470a57daceff2cd0632e348cf5b975d10977
- [42] ruyi-imager release list — https://github.com/ruyisdk/ruyi-imager/releases
- [43] ruyi release list — https://github.com/ruyisdk/ruyi/releases
- [44] packages-index commit list — https://github.com/ruyisdk/packages-index/commits/main
- [45] buddy-mlir main branch commit list — https://github.com/buddy-compiler/buddy-mlir/commits/main
- [46] buddy-mlir PR #1062 enable dump() for LLVM — https://github.com/buddy-compiler/buddy-mlir/pull/1062
- [47] buddy-mlir PR #1061 separate DeepSeek tokenizer from chat template — https://github.com/buddy-compiler/buddy-mlir/pull/1061
- [48] buddy-mlir PR #833 PaddleOCR-VL-0.9B integration — https://github.com/buddy-compiler/buddy-mlir/pull/833
- [49] buddy-mlir PR #945 w8a8 per-token dynamic quantization — https://github.com/buddy-compiler/buddy-mlir/pull/945
- [50] buddy-mlir PR #993 tile.upsample_nearest — https://github.com/buddy-compiler/buddy-mlir/pull/993
- [51] buddy-mlir PR #1059 memref copy changed to vector transfer — https://github.com/buddy-compiler/buddy-mlir/pull/1059
- [52] ruyiai-daily 2026-11-17 — https://github.com/RuyiAI-Stack/ruyiai-daily/blob/main/daily-news-2026-11-17.md
- [53] ruyiai-daily commit e1e6cffe — https://github.com/RuyiAI-Stack/ruyiai-daily/commit/e1e6cffe8a97d0f7a2891f68f75cf6417a5b52f5
- [54] RISE Python Wheels PR #4895 triton 3.9.0 — https://github.com/riseproject-dev/python-wheels/pull/4895
- [55] RuyiAI official homepage — https://www.ruyiai.org/
- [56] RuyiAI blog page — https://www.ruyiai.org/blog.html
- [57] RuyiAI docs page — https://www.ruyiai.org/docs.html
- [58] Official website repo commit list — https://github.com/RuyiAI-Stack/ruyiai-stack.github.io/commits/main
- [59] RuyiSDK community latest topics — https://ruyisdk.cn/latest
- [60] Forum xv6-riscv course Part 3 — https://ruyisdk.cn/t/topic/2910
- [61] IREE v3.14.0 release notes — https://github.com/iree-org/iree/releases/tag/v3.14.0
- [62] arXiv cs.AR latest — https://arxiv.org/list/cs.AR/recent
Limitations
This issue’s window is 24 hours (11-17 04:30 to 11-18 04:30). On the GitHub side, Atom feeds and anonymous APIs were cross-checked; some repositories are counted via Atom. The pytorch fork’s default branch is riscv, with main serving only as an upstream mirror; the body describes each branch separately. XAME/ZTT v0.6 is a provisional-version extension, and its instruction encoding and profile may change later; this issue records only the state and verification results at the time of merge and does not imply acceptance by upstream LLVM. The RISC-V conclusions for IREE are taken from the v3.14.0 release notes and were not re-tested on hardware. On the external news side, Google News was scraped via a proxy, and eight sets of queries returned zero hits; it cannot be ruled out that Chinese-language media carried reports that were not indexed.