You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been working for a several packaged projects using ggml and received reports that app crashes on different end-users machines. From gathered data this is probably because compiled dll that is packaged with app contains AVX commands, which might not be supported on end-user CPU or OS.
I propose that we can add runtime checks of what end-users CPU actually capable of (AVX, F16C support, etc). We can add a new function like is_ggml_supported() which will return false if any required commands extension is missing. This could be handled by app to change it behavior or just print that device isn't supported, not just crash silently.
I've been working for a several packaged projects using ggml and received reports that app crashes on different end-users machines. From gathered data this is probably because compiled dll that is packaged with app contains AVX commands, which might not be supported on end-user CPU or OS.
I propose that we can add runtime checks of what end-users CPU actually capable of (AVX, F16C support, etc). We can add a new function like
is_ggml_supported()
which will return false if any required commands extension is missing. This could be handled by app to change it behavior or just print that device isn't supported, not just crash silently.The good example of how to implement all this checks is here:
https://github.com/Mysticial/FeatureDetector
The C API might look something like this:
The text was updated successfully, but these errors were encountered: