> "Personally, I would hate to use software which tells me to upgrade my GPU..." I think its a design decision for the underlying library. Is the behavior conf

> "Personally, I would hate to use software which tells me to upgrade my GPU..." I think its a design decision for the underlying library. Is the behavior configurable, or "hidden" from the the user? Is the fallback configurable on a library-wide basis, or a per-kernel basis? If you're writing or testing code and trying to make it work, you want it to explode in an elegant-ish manner, and tell you what to fix. If you're shipping code, you want control over how it fails, and you might want different things. What are my options? There's probably cases where a graceful or semi-graceful fallback would work. However, there's cases where the time spent in CPU mode would be embarrassingly long - to the point where your options really are "show a message" or "disable the function." I'm with the OP here - the caller should have a say in the situation which will make the behavior predictable as software or hardware changes.