Skip to content

Conversation

ikawrakow
Copy link
Owner

There is no point in using ik_llama.cpp without GGML_IQK_MUL_MAT.

Closes #456

@Nexesenex
Copy link
Contributor

Nexesenex commented May 25, 2025

There is actually a point to leave this as a legacy marking for your new quants, because it helps a lot with merging them on my fork, including the potential future ones, which are still compatible with only a few formatting adaptation with the mainline ggml framework, even if the ops are not.

I'm really good at shooting in my own foot! :D

@ikawrakow
Copy link
Owner Author

as a legacy marking

Legacy marking in what sense?

@Nexesenex
Copy link
Contributor

Nexesenex commented May 25, 2025

In the sense that even if the option is not used anymore to compile, it's pretty handy for your average enthusiast such as myself to still have the distinction in the code between IKL multmat dependent code and the rest of your code to help the merging with a mainline fork, at least on anything with a compatible part.

For now, everything is still quite clear, but as time will pass, the divergence between IKL and mainline will increase, and having at least the point of reference of what works (theoretically) and what doesn't with mainline of August 2024 is an invaluable help.

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.

Bug: no compilation without IQK_MULMAT
2 participants