{"action":"opened","issue":{"url":"https://api.github.com/repos/CNugteren/CLBlast/issues/139","repository_url":"https://api.github.com/repos/CNugteren/CLBlast","labels_url":"https://api.github.com/repos/CNugteren/CLBlast/issues/139/labels{/name}","comments_url":"https://api.github.com/repos/CNugteren/CLBlast/issues/139/comments","events_url":"https://api.github.com/repos/CNugteren/CLBlast/issues/139/events","html_url":"https://github.com/CNugteren/CLBlast/issues/139","id":211131937,"number":139,"title":"Unable to test/tune for CPU device in OS X (error code -54)","user":{"login":"mrTsjolder","id":3738082,"avatar_url":"https://avatars1.githubusercontent.com/u/3738082?v=3","gravatar_id":"","url":"https://api.github.com/users/mrTsjolder","html_url":"https://github.com/mrTsjolder","followers_url":"https://api.github.com/users/mrTsjolder/followers","following_url":"https://api.github.com/users/mrTsjolder/following{/other_user}","gists_url":"https://api.github.com/users/mrTsjolder/gists{/gist_id}","starred_url":"https://api.github.com/users/mrTsjolder/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mrTsjolder/subscriptions","organizations_url":"https://api.github.com/users/mrTsjolder/orgs","repos_url":"https://api.github.com/users/mrTsjolder/repos","events_url":"https://api.github.com/users/mrTsjolder/events{/privacy}","received_events_url":"https://api.github.com/users/mrTsjolder/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-03-01T16:21:17Z","updated_at":"2017-03-01T16:21:17Z","closed_at":null,"body":"I tried to install CLBlast on my 2011 macbook pro to come to the conclusion that most of the tests just skipped, stating `CLBlast: OpenCL error: clEnqueueNDRangeKernel: -54` which turns out to be a `CL_INVALID_WORK_GROUP_SIZE` (as I found out [here](https://streamcomputing.eu/blog/2013-04-28/opencl-error-codes/)).\r\n\r\nAfter some googling I [discovered](http://stackoverflow.com/questions/10065681/opencl-kernel-work-group-size-restriction) that the OpenCL implementation from Apple would only support a single worker for a CPU. I thought to be able to circumvent this issue by tuning, but that only lead to segmentation faults or just empty results (because parameters for the number of workers starts at 8)."}}
{"actor":{"display_login":"mrTsjolder"}}