Skip to content

releases : build CPU backend separately (windows) #13642

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 21, 2025
Merged

Conversation

slaren
Copy link
Member

@slaren slaren commented May 19, 2025

By building the CPU backend separately it is possible to use clang to compile it even with backends that require a different C/C++ compiler, such as CUDA, SYCL and Vulkan. Using clang to build the CPU backend is preferred since it tends to result in better performance than MSVC.

Additionally, the CPU backend and llama.cpp now are only built once when creating a release.

Test release: https://github.com/slaren/llama.cpp/releases/tag/b5425

@github-actions github-actions bot added the devops improvements to build systems and github actions label May 19, 2025
@slaren slaren merged commit d643bb2 into master May 21, 2025
2 checks passed
@slaren slaren deleted the sl/release-clang-cpu branch May 21, 2025 20:10
infil00p pushed a commit to baseweight/llama.cpp that referenced this pull request May 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devops improvements to build systems and github actions
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants