Repository navigation
Conversation
finnvoor
force-pushed
the
fix/metal-api-validation
branch
from
December 8, 2023 11:42
955a56d to
8def8ba
Compare
Member
|
I fixed this in 7bc4d22 Currently, only the softmax kernel requires optional |
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
2 participants
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.
The Metal API validator doesn't like setting nil for a buffer and throws error
failed assertion Compute Function(kernel_soft_max_4): missing buffer binding at index 1 for src1[0].Only setting non-nil buffers fixes the error, even though the binding is still "missing"