vulkan: throw system error instead of SIGABRT during init on older devices #16156
+7
−1
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 #16142
Main issue is
llama_supports_gpu_offload
should not get SIGABRT if backend can't initialize correctly inggml_vk_instance_init
. System error will make sure it is not added to registry anyway.Optionally, added catches in
ggml_backend_vk_reg
to returnnull
for any errors, unless this was intended to be handled upstream. In that case i can remove that commit.