Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Validate kllama Apple native-kernel fix (PR #315) on real iOS/macOS hardware

未关闭
  • 哪里不对？
#316 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
冷清
技术栈
kotlin
领域
mobile-dev, performance

调研方向

The remaining work is a before/after packed-quant matmul throughput comparison on real Apple hardware; the issue does not name a benchmark file or command. First read PR #315 and the engine’s #958/#959 performance results, then locate the benchmark entry point. Record comparable results for the old stub and the fix on an Apple Silicon device; simulator or compile results alone do not meet the stated goal.

由索引模型根据 Issue 内容生成。

描述

help wanted

Context

PR #315 fixed llm-runtime/kllama's PlatformNativeKernels.ios.kt/.macos.kt,
which were stale no-op stubs — both cited SKaiNET#959 as "not shipped yet" when
it had in fact shipped, meaning kllama's registerPlatformBackends() facade
was silently leaving packed-quant matmul on the scalar floor on iOS and macOS,
despite the engine's native-cinterop NEON/Accelerate kernels being built and
available.

The fix itself (calling installNativeKernels(), mirroring linuxMain's
actual) was written and reviewed, but could not be compiled or run in the
session that produced it — that environment was Linux only, and Kotlin/Native
requires a macOS host to compile Apple targets at all. Verification there was
limited to code review and cross-target compilation (jvm/linuxX64/android/js).

What needs a Mac

  • ./gradlew :llm-runtime:kllama:compileKotlinIosArm64 :llm-runtime:kllama:compileKotlinIosSimulatorArm64 :llm-runtime:kllama:compileKotlinMacosArm64 — confirm the fix actually compiles (the installNativeKernels() import/call was written against the API but never type-checked on an Apple target). Update: it did not compile as originally written — implementation(libs.skainet.backend.nativeCpu) was still scoped to linuxMain only, not nativeMain, so macosMain/iosMain never got the dependency. Fixed in PR #315 commit 9bb3707; all three Apple targets now compile.
  • At runtime, confirm KernelRegistry.bestAvailable()?.name (or equivalent) reports native-cinterop on iOS/macOS after registerPlatformBackends() runs, not scalar. Confirmed via KernelRegistry.availableNames() on both macosArm64Test and iosSimulatorArm64Test: reports [native-cinterop].
  • A real before/after comparison: packed-quant matmul throughput with the old no-op stub vs. the fix, on an actual Apple Silicon device/simulator — the engine's own NEON/cinterop work (#958/#959) reported real numbers on Android-equivalent hardware; this fix has none yet for Apple.
  • Run kllama's existing test suite on iosSimulatorArm64Test/macosArm64Test (both currently skip on CI/Linux — kotlin.native.ignoreDisabledTargets). Both green, including the cross-target SmolLm2InferenceSpike (commonTest).

Related

  • Fixed by #315
  • Exercised end-to-end by SKaiNET-examples' KernelRace sample — see SKaiNET-examples#33, which needs this issue resolved before its iOS build shows real NEON acceleration instead of scalar.

Good fit for whoever on the team has a Mac + Xcode handy — no deep kernel-SPI knowledge needed, mostly "build it, run it, check the numbers." Remaining: real-device throughput numbers (needs physical hardware time, not just simulator/compile verification).

主要语言
Kotlin
星标
8
派生
3
平均合并
1 天 20 小时
30 天内合并 PR
44

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

SKaiNET-developers/SKaiNET-transformers 的其他 Issue

查看 SKaiNET-developers/SKaiNET-transformers 的全部 Issue

相似的 Issue

更多 Kotlin Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。