Qualcomm AI Engine Direct - Fixed the wrong size for memmove in kv_manager#14685
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/14685
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 New Failure, 2 Unrelated FailuresAs of commit 9ea1583 with merge base ebf4c12 ( NEW FAILURE - The following job has failed:
FLAKY - The following job failed but was likely due to flakiness present on trunk:
BROKEN TRUNK - The following job failed but was present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
@pytorchbot cherry-pick --onto release/1.0 -c regression |
This PR needs a
|
|
Can you share more details in terms of what we're fixing? |
| // copy from first dimension | ||
| for (int i = 0; i < metadata_.head_dim; i++) { | ||
| std::memmove(k_cache_in_write_ptr, k_cache_in_read_ptr, dst_cache_num); | ||
| std::memmove( |
…nager (pytorch#14685) As title. cc: @haowhsu-quic , @winskuo-quic
As title.
cc: @haowhsu-quic , @winskuo-quic