Research window: Past 24 hours (2026-09-22 04:30 ~ 2026-09-23 04:30, Beijing time). Sources: Three GitHub organization checks (RuyiAI-Stack 17 repos, ruyisdk 46 repos, openRuyi-Project 36 repos — commits, Releases, and non-default branch pushes via both API and Atom channels; upstream fork commits filtered item-by-item against RISC-V keywords, unrelated commits excluded), RuyiSDK developer community (latest forum topics), openRuyi distro news page, board support matrix and example repo docs, ruyi-tuner dev branch, tech intelligence repo, arXiv search, Google News RSS multi-query in Chinese and English (via proxy; no hits this window, see appendix).

Index

  • Today’s Highlight: RuyiSDK Appears at 2026 Yunqi Conference Ruyi Community Booth (09-22)
  • I. RuyiAI Stack Progress (PyTorch / Triton / TileLang RISC-V Porting)
    • 1.1 PyTorch fork: no RISC-V feature commits in window; riscv branch silent, 8 open PRs unchanged (09-22 status)
    • 1.2 triton-riscv, tilelang-riscv, and dedicated target repos silent in window (since 09-21)
    • 1.3 Tech intelligence repo pushes 09-22 issue; site contributor data auto-updated (09-22)
  • II. RuyiSDK Toolchain and Distro (GCC, kernel, support matrix, openRuyi)
    • 2.1 Compiler tuning tool RuyiTuner implements project-level search: aggregated-fitness genetic algorithm lands in v1.x branch (09-22)
    • 2.2 Support matrix adds Fedora 44 report for SiFive Premier P550; CH32V307 updated to RT-Thread BSP 5.3.1 (09-22)
    • 2.3 board-docs adds Premier P550 docs; CoM260 Kit completes ROS 2 chapters 3 and 4 plus TOC references (09-22)
    • 2.4 ruyi, packages-index, and riscv-gcc silent in window; ruyi-backend routine dependency upgrades (09-22)
    • 2.5 openRuyi and openRuyi-Project orgs: no commits in window (09-22 status)
  • III. Vector Extensions and Operator Optimization (VecIntrinBench / IntrinTrans / FBGEMM)
    • 3.1 All three dedicated target repos silent in window (09-22 status)
  • IV. Community and Events (biweekly progress, forum, docs)
    • 4.1 Biweekly Progress Issue 077 enters integration phase: targeting 09-24 release, draft aggregates P extension and V8 progress (09-22)
    • 4.2 Forum adds two topics: Yunqi Conference recap and repost of Zhaosong MCULib-FuSa automotive certification (09-22)
    • 4.3 openRuyi news page: no new announcements; latest published biweekly progress remains 076 (09-22 status)
  • V. Trend Observations
    • 5.1 Compiler tuning moves from single-file to project-level: roadmap signal from RuyiTuner v1.8
    • 5.2 Releases and events enter a dense week: Yunqi Conference (through 09-24) overlaps with Biweekly 077 (09-24)
    • 5.3 Two ends of board validation: application-level P550 and MCU-level CH32V307 advance in parallel
    • 5.4 Gaps and watch points in this window

Today’s Highlight: RuyiSDK Appears at 2026 Yunqi Conference Ruyi Community Booth

Date: 2026-09-22　Source: Community post 2849

At 18:31 Beijing time on 09-22, the RuyiSDK developer community announced that the 2026 Yunqi Conference opened that day, with RuyiSDK appearing at the conference’s Ruyi Community booth. The booth showcased to industry partners and RISC-V developers a one-stop RISC-V software development kit, toolchain, package manager, IDE development plugins, and multi-hardware-platform adaptation results, with live hands-on demos and technical exchange on site, drawing attendees from low-level technology, chip, and AI fields to stop and try it out; the post includes multiple on-site photos. According to the community, visitors can intuitively see through on-site video how RuyiSDK connects ecosystem resources such as development boards, operating systems, toolchains, and software packages, providing a unified and convenient entry point for RISC-V development.

The conference runs through 09-24, and the booth will continue technical demos, one-on-one Q&A, and community interaction. The draft of Biweekly Progress Issue 077, formed the same evening (see 4.1), has also included this appearance in its “Community Updates” section, indicating this is an external showcase milestone the biweekly report plans to cover. For developers following RuyiSDK’s adoption, 09-22 through 09-24 is a window to obtain first-hand information on site or through follow-up coverage.

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

Window Overview: Of the 17 repositories in the RuyiAI-Stack organization, 3 had pushes during the window: pytorch (main upstream sync), ruyiai-daily (1 push), and ruyiai-stack.github.io (1 push); triton-riscv, tilelang-riscv, llvm-project, pytorch-ci, FBGEMM, cpuinfo, VecIntrinBench, IntrinTrans, harness, dsh-osc, torq-tile, and skills all had no pushes during the window.

1.1 No RISC-V feature commits in the PyTorch fork during the window: riscv branch silent, 8 open PRs with no updates (09-22 status)

Date: 2026-09-22　Source: riscv branch commits, PR list

The fork’s riscv branch had no new commits during the window: the branch head remains 4f173e3e (Fix bytes_to_scalar for float/complex on RISC-V, corresponding to the content of PR #44/#10), with its visible timestamp frozen at the evening of 09-20; the update timestamps of the 8 open merge requests (#23, #35, #36, #38, #43, #46, #48, #51) remain unchanged at 09-21 08:24, reflecting the baseline refresh action from the previous day’s window, with no new merges, no newly opened PRs, and no closures during the window. In contrast to the “force-push reshuffling” cadence of the prior two days, the branch was completely static this period.

The main branch had 20 upstream sync commits during the window, covering routine topics (ROCm test enablement, inductor max_pool fixes, distributed test reuse, symm_mem stream serialization, etc.); filtering each one by keywords such as riscv, rvv, vector, XuanTie, rv64, and rv32 yielded no RISC-V-related content, so they are not covered in this issue. The two pending RVV patches (#46 ATen RVV support, #48 RVV CPU capability) remain unmerged, with their pending status now spanning four reporting windows.

1.2 triton-riscv, tilelang-riscv, and dedicated target repositories silent during the window (since 09-21)

Date: 2026-09-22　Source: triton-riscv, tilelang-riscv, llvm-project

No new activity on the compiler and operator porting front this period: triton-riscv commits stopped at 09-14 (the most recent nightly build, 2026-09-20, was already covered the previous day, with no new releases during the window); tilelang-riscv stopped at 07-16, and the llvm-project fork stopped at 09-17; harness (09-10), dsh-osc (09-15), and pytorch-ci (08-31) were also silent. None of the three repositories had any commits or releases during the window.

1.3 Tech intelligence repository pushed the 09-22 issue, site contributor data auto-updated (09-22)

Date: 2026-09-22　Source: ruyiai-daily commit e29520b2, 2026-09-22 issue content

The tech intelligence repository completed one commit during the window (Beijing time 09-22 06:19), covering the 09-22 issue, whose self-described rolling window is 09-21 05:32 to 09-22 06:00. The RISC-V section of this issue includes: the Zifencei ordering semantics revision merged (extending FENCE.I ordering of prior accesses to instruction fetches, serving JIT and self-modifying code scenarios), the SpacemiT RVV vision preprocessing merge (vectorized path for BGR→NCHW and grayscale fused packing), XiangShan FPGA-Diff adding the GBus host interface and UVHS adaptation, NutShell workload and restorer unified build pipeline, and the XiangShan prefetch.i retirement fix (eliminating a correctness issue that could hang the ROB head), among other items; the original timestamps of the above items mostly fall before this window, and per the no-duplication principle they are not expanded upon in this issue, with only the publication action recorded. The site repository had one additional automated commit during the window (Beijing time 09-23 03:34), routinely updating the contributor data file.

II. RuyiSDK Toolchain and Distributions (GCC, Kernel, Support Matrix, openRuyi)

Window Overview: Of the 46 repositories in the ruyisdk organization, 5 had pushes during the window: ruyi-tuner (v1.x development branch), support-matrix, board-docs, wechat-articles, and ruyi-backend (routine Dependabot). The latest activity for riscv-gcc, ruyi, packages-index, docs, linux-xuantie-kernel, ruyisdk-vscode-extension, ruyisdk-website, ruyisdk-overlay, and others all dates to 09-21 or earlier. No repositories in the openRuyi-Project organization had any pushes during the window.

2.1 Compiler Tuning Tool RuyiTuner Implements Project-Scope Search: Aggregated-Fitness Genetic Algorithm Lands in v1.x Branch (09-22)

Date: 2026-09-22　Source: v1.x commit d2367ec0, CHANGELOG

At 15:59 Beijing time on 09-22, RuyiTuner, the automatic compiler tuning tool under the ruyisdk organization, merged a medium-sized commit into the v1.x development branch (+274/-154 lines, covering 6 files including CHANGELOG, Readme, RunCSiBE docs, and scripts/utils/GA.py): Implement project-scope search with aggregated-fitness GA and update docs, formally implementing project-scope search mode.

Per the CHANGELOG, this constitutes a 1.8 release change. There are three key points: First, utils/GA.py extracts a generic genetic algorithm search core _ga_search and adds a new project-level function LeverageSyner_GA_codesize_project—the fitness function changes from “single-file instruction count reduction ratio” to “file-size-weighted overall reduction rate (Σbaseline−Σoptimized)/Σbaseline,” searching for a single common optimal pass sequence for the entire project. Second, the single-file version function is correspondingly renamed to LeverageSyner_GA_codesize_file, matching the project version, with run.py calls updated accordingly (the --search_scope parameter was previously a placeholder marked “not yet implemented,” now completed in this cycle). Third, on engineering details, when a sequence fails to opt on individual files, it falls back to the original IR count, and a new “(file, sequence) → size” cache is added to reduce redundant opt runs. The CLI is indirectly connected as a result: ruyituner.py removes the placeholder notice, and project mode can now complete the full training-plus-optimization workflow.

RuyiTuner positions itself as an “LLVM tuning tool based on optimization synergy analysis”: it is not bound to a specific LLVM version or target architecture (determined by the target triple of the input IR, naturally covering both x86 and RISC-V), and through empirical measurement it mines synergy pairs where “the combined effect exceeds the sum of individual passes,” then uses a genetic algorithm to search within the space formed by synergy pairs for the optimization sequence with the best code size. The accompanying RunCSiBE.md documents the measured average optimization rates of nineteen CSiBE v2.1.1 benchmark projects on LLVM 22.1.0-rc2 x86 and RISC-V toolchains, such as 53.94% on the RISC-V side for the compiler project; this document now also adds usage examples for --search_scope. The repository is continuously maintained by community developers (established in late August, Apache-2.0), and this update is its first inclusion in the daily briefing within the ruyisdk organization.

2.2 Support Matrix Adds Fedora 44 Report for SiFive Premier P550, CH32V307 Updated to RT-Thread BSP 5.3.1 (09-22)

Date: 2026-09-22　Source: PR #400, PR #404

The development board support matrix merged two reports during the window: First (submitted at 21:41 Beijing time on 09-22), a new Fedora 44 Server test report for the SiFive HiFive Premier P550, adding another distribution family to its existing Debian, Ubuntu, and other system entries—this is also the P550 board’s consecutive action following the previous window’s “Debian report update.” Second (09-22 14:35), the CH32V307 (WCH RISC-V MCU) RT-Thread report was updated to the official BSP 5.3.1 version. The two correspond respectively to PR #400 and #404 entries in the biweekly report issue 077 draft (see 4.1).

2.3 board-docs Adds Premier P550 Documentation, CoM260 Kit Completes ROS 2 Chapters 3 and 4 with Catalog References (09-22)

Date: 2026-09-22　Source: PR #46, PR #48

The development board examples repository had 4 commits during the window: new HiFive Premier P550 Chinese and English board documentation with HelloWorld and CoreMark examples (PR #46, 16:35 Beijing time on 09-22); followed by two commits introducing the ROS 2 catalog from the course repository into the board documentation and preserving inline metadata with a fix commit (16:20 and 17:17); finally merging PR #48 (18:35), completing ROS 2 Chapters 3 and 4 for the CoM260 Kit and referencing the ROS 2 catalog. At this point, the repository has rolled out documentation and examples simultaneously for two board lines—the K3 platform (CoM260 Kit, K3 Pico-ITX) and the P550—within one week, forming a companion set with the two support matrix reports from the same day.

2.4 ruyi, packages-index, and riscv-gcc Silent During Window; ruyi-backend Routine Dependency Upgrades (09-22)

Date: 2026-09-22　Source: ruyi Releases, riscv-gcc 16.2 branch

After the package manager ruyi released 0.54.0-alpha.20260918 in the previous period, there were no new commits or new Releases during the window; the installable stable version remains 0.52.0. The software package index packages-index’s last commit is dated 09-16. Neither of riscv-gcc’s two active branches, 16.2 and p-rebase, had new commits during the window (the latest remains the 09-21 merge of SpacemiT X100/A100 core support and P extension lowering, which was the previous day’s window result). ruyi-backend had 3 commits during the window, all routine Dependabot upgrades: SQLAlchemy 2.0.52→2.0.54 (PR #127) and Ruff 0.16.8 (PR #128), with no functional changes.

2.5 openRuyi and openRuyi-Project Organizations Have No Commits During Window (09-22 Status)

Date: 2026-09-22　Source: openRuyi commit history

The last commit to the openRuyi software package catalog remains 09-22 01:46 (dual-track upgrades of linux 7.2.6 and linux-lts 6.18.52, etc., already covered the previous day). During the window, all 36 repositories in the organization had no pushes; the linux worktree’s ruyi/7.2.y and other branches likewise remain at 09-21. After consecutive days of high-frequency commits, this distribution has entered a quiet window, followed by the observation point of this month’s release (2026.09) announcement.

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

3.1 All Three Dedicated Target Repositories Silent During Window (09-22 Status)

Date: 2026-09-22　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 (latest push record 06-24), IntrinTrans was 06-25, and the FBGEMM fork was 07-13; the same group’s observation targets cpuinfo (05-20) and torq-tile (04-09) were likewise silent. The most recent reproducible result in this direction remains the ONNX Runtime MLAS RVV kernel optimization covered on 09-17 (3.01× speedup on ResNet50 on K3/X100); tuning-related tool-side progress has shifted to RuyiTuner in 2.1.

IV. Community and Events (Biweekly Progress, Forum, Documentation)

4.1 Biweekly Progress Issue 077 Enters Integration Phase: Targeting 09-24 Release, Draft Consolidates P Extension and V8 Progress (09-22)

Date: 2026-09-22　Source: Issue 077 draft, summary commit #358

Preparation for the release of Biweekly Progress Issue 077 intensified within the window: starting from the initialization of the Issue 077 draft in the wechat-articles repository at 09:44 Beijing time on 09-22, 7 consecutive commits (#352 to #358) were made within 9 hours, successively adding IDE updates, development board news, and content for various components, and completing the main summary commit. The draft file is named 20260924-ruyisdk-biweekly-77.md, with the title marked “September 24, 2026,” indicating a planned release on 09-24 (Thursday); as of the end of the window, the draft was still being integrated, and the official content is subject to the released version.

Key points already consolidated in the draft (for early reference, all subject to the official 09-24 version): 16 new RuyiSDK IDE features (transparent sidebar icons, semantic version sorting, installation progress display, virtual workspace detection, esbuild bundling and workspace security restrictions, etc.); entries for development board support matrix and example repositories PR #400 to #405, #46 to #47; on the LLVM side, the RISC-V P extension series merges and pending patches (packed widening add accumulate, Packed Load/Store/Element Insert/Join, scalar saturation and bit-reversal builtins, packed saturation operations, as well as RVA23.1/RVB23.1 experimental profiles, HINVAL extension dependency fixes, etc., totaling 15 items, of which 2 are still under review); on the V8 side, this issue’s highlight is code generation optimization for Word32 equality/inequality comparisons—ahead-of-time (AOT) builtin library static code size reduced by 2.7%, plus 13 merged patches and 3 review-merged patches listed. Compared to the previous practice of “visible only on release day,” this issue’s information is visible in advance, reflecting a stable community operation rhythm.

4.2 Two New Forum Topics: Yunqi Conference Report and Repost of MegaSoar MCULib-FuSa Automotive Certification (09-22)

Date: 2026-09-22　Source: Community post 2849, Community post 2848

Two new topics were added to the RuyiSDK developer community within the window: the first is a report on the Yunqi Conference appearance published at 18:31 on 09-22 (see “Today’s Highlights”); the second is a repost at 12:03 on 09-22—MegaSoar Technology (Wuhan) released the functional safety C runtime library MCULib-FuSa, certified by SGS to comply with ISO 26262, paired with the ZCC-FuSa compiler to provide an ASIL D solution for RISC-V automotive software development. The latter is an industry development in the RISC-V automotive foundational software ecosystem, and the community included it in the news section outside the RuyiAI board. Neither post had any replies within the window.

4.3 No New Announcements on openRuyi News Page; Latest Published Biweekly Progress Issue Remains 076 (09-22 Status)

Date: 2026-09-22　Source: openRuyi news page, Biweekly Progress Issue 076

The openRuyi news page had no updates within the window, with the latest article still being the 2026.08 version announcement (no preview or release for the 2026.09 monthly version yet); the latest published issue of RuyiSDK Biweekly Progress on the forum remains Issue 076 (09-15), with Issue 077 in the draft integration phase (see 4.1).

V. Trend Observations

5.1 Compiler tuning moves from single-file to project-level: the roadmap signal from RuyiTuner v1.8

The project-level search (2.1) added to RuyiTuner in this issue is worth reading together with the previous two reports: 09-21 was the GCC side filling in -mcpu/-mtune for SpacemiT X100/A100 (the toolchain “recognizing the core”), 09-17 was the measured RVV kernel numbers for ONNX Runtime (operators “running faster”), and this issue hands “how to choose the optimization sequence” to a genetic algorithm for project-level automatic tuning (with gains “landing on whole-package size”). Together the three sketch out a complete chain on the compiler side of RuyiSDK: core recognition → operator optimization → sequence tuning. The project-level mode elevates the evaluation metric from single-file to whole-package weighted, directly matching the real demand for “whole-package size” in software distribution; the next thing worth tracking is whether it gets incorporated into the official RuyiSDK toolchain distribution, along with the expansion of the RISC-V dataset side (datasets/ll_files/riscv) and the pace of adaptation to new LLVM versions.

5.2 Releases and events enter a dense week: Yunqi Conference (through 09-24) overlapping with Biweekly Report 077 (09-24)

This window opens two outward-facing timelines at once: 09-22 saw the Yunqi Conference kick off, with the Ruyi community booth open through 09-24; the same evening, the 077th biweekly report completed integration, with release planned for 09-24. Stacked on top of the previous week’s content loop for the K3/CoM260 platform (report, examples, course) and the newly added P550 board report, RuyiSDK’s “external visibility” reaches a recent high over the three days from 09-22 to 09-24: offline there is a conference booth, online there are the biweekly report and support matrix updates. Attention naturally falls on whether the official 09-24 biweekly report announces a new ruyi version number (the state after the 0.54.0-alpha pre-release line) and on the follow-up outcomes of discussions at the Yunqi Conference.

5.3 Both ends of board validation: application-level P550 and MCU-level CH32V307 advance in parallel

The two reports in this issue’s support matrix cover the two endpoints respectively: SiFive Premier P550 (application-level, capable of running Fedora 44 Server) and CH32V307 (MCU-level, RT-Thread BSP 5.3.1). Combined with the multi-OS reports for K3/CoM260 and the synchronized completion of P550 documentation and examples, RuyiSDK’s board support matrix is rolling forward across the entire span from “application processor to MCU,” and the completeness of the supporting assets for each newly added board (system report, board documentation, example code, course entry point) is improving. For teams that use development boards as their delivery vehicle, this means reproducible materials beyond the toolchain are thickening.

5.4 Gaps and points of attention in this window

Gaps that must be recorded honestly: the PyTorch fork saw no functional-side progress whatsoever (both the riscv branch and the 8 open PRs went silent, and the two RVV patches continue to wait); triton-riscv, tilelang-riscv, and the vector-operator dedicated target repositories were all silent; ruyi and packages-index had no commits or releases; the openRuyi organization entered a quiet window; on the news side, multiple Google News queries in Chinese and English for RuyiAI, RuyiSDK, the Ruyi community, and openRuyi returned zero hits in a row, and there were no new arXiv entries within the window. Points of attention: first, follow-up developments at the Yunqi Conference booth on 09-23 to 09-24; second, the official release of Biweekly Progress No. 077 on 09-24 and whether it brings a ruyi version milestone; third, updates to the actual benchmark numbers for RuyiTuner’s project-level search and the possibility of its inclusion in the official toolchain; fourth, the openRuyi 2026.09 monthly release announcement.

Source Verification Table

Source Verification Result
RuyiAI-Stack organization (17 repos) 3 repos had activity: pytorch (20 upstream syncs on the main branch, riscv branch silent), ruyiai-daily (09-22 issue), ruyiai-stack.github.io (contributor data); the remaining 14 repos were silent
ruyisdk organization (46 repos) 5 repos had pushes: ruyi-tuner (v1.x branch, project-level search), support-matrix (2 commits), board-docs (4 commits), wechat-articles (7 commits, issue 077 draft), ruyi-backend (Dependabot); ruyi, packages-index, and riscv-gcc had no commits or releases
openRuyi-Project organization (36 repos) No pushes at all within the window; latest commit was 09-22 01:46 (previous day’s window)
RuyiSDK community forum 2 new topics (Yunqi Conference, Zhaosong certification repost); no new biweekly progress posts
openRuyi news page No new version announcement (latest remains 2026.08)
Development board support matrix 2 commits: P550 Fedora 44 report (PR #400), CH32V307 updated to RT-Thread BSP 5.3.1 (PR #404)
Development board examples repository 4 commits: P550 documentation and examples (PR #46), ROS 2 directory references, CoM260 chapters 3/4 (PR #48)
Tech intelligence repository (ruyiai-daily) 09-22 issue committed (5 items in the RISC-V section, mostly timestamped before the window); site contributor data auto-updated
arXiv (RISC-V vector and AI compilers) No new entries within the window (most recent was the 09-19 entry)
Google News RSS (multiple Chinese and English queries) Zero hits for RuyiSDK / RuyiAI / Ruyi community / openRuyi / Yunqi Conference × Ruyi community; control queries in the same batch returned normally, ruling out a scraping failure

Complete Source List