Avoid using __fp16 on ARM with old nvcc, fixes #10555 #10616
Merged
Conversation
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
github-actions
bot
added
the
ggml
frankier
force-pushed
the
fix-nvcc-cuda11-arm
branch
from
9a240e6 to
407fba8
Compare
frankier
force-pushed
the
fix-nvcc-cuda11-arm
branch
from
407fba8 to
dca39b0
Compare
slaren
approved these changes
Dec 4, 2024
tinglou
pushed a commit
to tinglou/llama.cpp
that referenced
this pull request
Dec 7, 2024
arthw
pushed a commit
to arthw/llama.cpp
that referenced
this pull request
Dec 20, 2024
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.
Fixes #10555
It appears that NVCC on CUDA <= 11 doesn't have __fp16, so as I understand it this should fallback to a default slower implementation.