Halaman utama Jelajahi Bantuan
Daftar Masuk
OpenSource
/
ollama
2
0
Fork 0
Berkas Masalah 0 Permintaan Tarik 0 Wiki
Cabang: main
Ranting Tag
ollama
/
llama
Patrick Devine ef378ad673 gemma3 quantization (#9776) 1 bulan lalu
..
llama.cpp ef378ad673 gemma3 quantization (#9776) 1 bulan lalu
patches ef378ad673 gemma3 quantization (#9776) 1 bulan lalu
.gitignore 96efd9052f Re-introduce the `llama` package (#5034) 6 bulan lalu
README.md b901a712c6 docs: improve syntax highlighting in code blocks (#8854) 2 bulan lalu
build-info.cpp d7d7e99662 llama: update llama.cpp vendor code to commit d7cfe1ff (#9356) 2 bulan lalu
build-info.cpp.in 5b446cc815 chore: update gitattributes (#8860) 2 bulan lalu
llama.go e093db92c4 sample: temporarily use grammars for constrained generation in new engine (#9586) 1 bulan lalu
llama_test.go 61676fb506 llama: move grammar tests to llama_test.go (#8411) 3 bulan lalu
mllama.cpp d7d7e99662 llama: update llama.cpp vendor code to commit d7cfe1ff (#9356) 2 bulan lalu
mllama.h c7cb0f0602 image processing for llama3.2 (#6963) 6 bulan lalu
sampling_ext.cpp e093db92c4 sample: temporarily use grammars for constrained generation in new engine (#9586) 1 bulan lalu
sampling_ext.h e093db92c4 sample: temporarily use grammars for constrained generation in new engine (#9586) 1 bulan lalu

README.md

llama

This package provides Go bindings to llama.cpp.

Vendoring

Ollama vendors llama.cpp and ggml. While we generally strive to contribute changes back upstream to avoid drift, we carry a small set of patches which are applied to the tracking commit.

If you update the vendoring code, start by running the following command to establish the tracking llama.cpp repo in the ./vendor/ directory.

make -f Makefile.sync apply-patches

Updating Base Commit

Pin to new base commit

To change the base commit, update FETCH_HEAD in Makefile.sync.

When updating to a newer base commit, the existing patches may not apply cleanly and require manual merge resolution.

Start by applying the patches. If any of the patches have conflicts, the git am will stop at the first failure.

make -f Makefile.sync apply-patches

If there are conflicts, you will see an error message. Resolve the conflicts in ./vendor/, and continue the patch series with git am --continue and rerun make -f Makefile.sync apply-patches. Repeat until all patches are successfully applied.

Once all patches are applied, commit the changes to the tracking repository.

make -f Makefile.sync format-patches sync

Generating Patches

When working on new fixes or features that impact vendored code, use the following model. First get a clean tracking repo with all current patches applied:

make -f Makefile.sync clean apply-patches

Iterate until you're ready to submit PRs. Once your code is ready, commit a change in the ./vendor/ directory, then generate the patches for ollama with

make -f Makefile.sync format-patches

In your ./vendor/ directory, create a branch, and cherry-pick the new commit to that branch, then submit a PR upstream to llama.cpp.

Commit the changes in the ollama repo and submit a PR to Ollama, which will include the vendored code update with your change, along with the patches.

After your PR upstream is merged, follow the Updating Base Commit instructions above, however first remove your patch before running apply-patches since the new base commit contains your change already.