Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Allow specifying p scale factor for ggml rope and rope_back ops #1967
Allow specifying p scale factor for ggml rope and rope_back ops #1967
Changes from 2 commits
bc17e11
4bf45a7
887694a
e92795f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use
memcpy
to store the params so we can all sleep well knowing this is not UB :)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need to extend the API - add
p_scale
to originalggml_rope_xxx()
and add comment to usep_scale == 1.0f
for regular computation. AddGGML_ASSERT(p_scale == 1.0f)
in backward callThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Won't this break every single thing that currently uses the llama.cpp version of GGML?
What do you think about using a define to enable the p_scale argument for rope and having it be off by default? That way existing stuff can opt in.
It might also be worth thinking about adding something like
GGML_API_VERSION
which could be bumped when incompatible changes occur, so stuff building against GGML could handle API changes more gracefully.