add missing kv clear in llama_beam_search#6664
Merged
compilade merged 1 commit intoggml-org:masterfrom Apr 14, 2024
Merged
Conversation
Contributor
Author
|
cc @mattpulver, who added beam search in #2267. |
compilade
approved these changes
Apr 14, 2024
Collaborator
compilade
left a comment
There was a problem hiding this comment.
Nice catch!
Throwing an idea here for later: I think the beam search should eventually be adapted to use one seq_id per beam to facilitate the logic for sharing KV cells between beams, and to allow parallel beam search.
Contributor
Author
I agree! |
Seunghhon
pushed a commit
to Seunghhon/llama.cpp
that referenced
this pull request
Apr 26, 2026
phuongncn
pushed a commit
to phuongncn/llama.cpp-gx10-dgx-sparks-deepseekv4
that referenced
this pull request
Apr 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds a call to
llama_kv_cache_seq_rm()inllama_beam_search_data::fill_next_beams_by_top_probabilities().This seems to be necessary for the subsequent
llama_decode()calls -- which can act on the same sequence at the same position with different test tokens -- to return reasonable results.Before this change:
After this change: