Skip to content

Build on official llama.cpp; vendor the decision engine - #6

Merged
yogthos merged 3 commits into
mainfrom
upstream-llama
Oct 15, 2026
Merged

yogthos merged 3 commits into
mainfrom
upstream-llama

Conversation

@yogthos

@yogthos yogthos commented Oct 15, 2026

Copy link
Copy Markdown
Member

The parallel-decision fork changed nothing in libllama: its decision engine runs on the stock API. So native/decision-engine.{h,cpp} now carries the engine, trimmed to the class lev_decision.cpp drives (the fork's schema compiler and server glue are left out), and llama.cpp is pinned at official release b11630, 589 commits past the fork's base. Upstream dropped the two common/ batch helpers the engine used; they are kept locally. The engine stays vendored until ggml-org/llama.cpp#29752 lands.

Measured back to back against the fork's library: the answers don't move (authored144 108/144, ECE 0.174 on both; llm-test, think-test and clef-test pass against their goldens), and upstream is 3-15% faster on every Jev workflow row. Numbers are in bench/README.md.

The release workflow, run on this branch with jolt nightly (JOLT_PIN=vnightly, which has jolt-lang/jolt#1341 and #1343), builds and self-tests the binary on mac and linux: run 38675927682.

Also: prepare_test now finds the checkpoints the way jolt prepare does, so config.edn's :checkpoints-home counts, not just LEV_CHECKPOINTS or ../laya.

The parallel-decision fork changed nothing in libllama: its engine runs on
the stock API. native/decision-engine.{h,cpp} is that engine (the class
lev_decision.cpp drives, without the fork's schema compiler and server
glue), with the two common/ batch helpers upstream dropped kept locally.
llama.cpp is pinned at release b11630, 589 commits past the fork's base,
until ggml-org/llama.cpp#29752 lands.
It read LEV_CHECKPOINTS or ../laya and ignored config.edn's
:checkpoints-home, which jolt prepare honours.
@yogthos
yogthos merged commit 5f76b73 into main Oct 15, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant