{"action":"created","issue":{"url":"https://api.github.com/repos/RadeonOpenCompute/ROCm/issues/330","repository_url":"https://api.github.com/repos/RadeonOpenCompute/ROCm","labels_url":"https://api.github.com/repos/RadeonOpenCompute/ROCm/issues/330/labels{/name}","comments_url":"https://api.github.com/repos/RadeonOpenCompute/ROCm/issues/330/comments","events_url":"https://api.github.com/repos/RadeonOpenCompute/ROCm/issues/330/events","html_url":"https://github.com/RadeonOpenCompute/ROCm/issues/330","id":295474197,"number":330,"title":"clinfo wrongly reports max work group size 256","user":{"login":"preda","id":706426,"avatar_url":"https://avatars1.githubusercontent.com/u/706426?v=4","gravatar_id":"","url":"https://api.github.com/users/preda","html_url":"https://github.com/preda","followers_url":"https://api.github.com/users/preda/followers","following_url":"https://api.github.com/users/preda/following{/other_user}","gists_url":"https://api.github.com/users/preda/gists{/gist_id}","starred_url":"https://api.github.com/users/preda/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/preda/subscriptions","organizations_url":"https://api.github.com/users/preda/orgs","repos_url":"https://api.github.com/users/preda/repos","events_url":"https://api.github.com/users/preda/events{/privacy}","received_events_url":"https://api.github.com/users/preda/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-02-08T11:18:12Z","updated_at":"2018-02-20T14:56:29Z","closed_at":null,"author_association":"NONE","body":"ROCm 1.7, Ubuntu 17.10, Vega 64:\r\nclinfo reports:\r\n Max work items dimensions:\t\t\t 3\r\n    Max work items[0]:\t\t\t\t 1024\r\n    Max work items[1]:\t\t\t\t 1024\r\n    Max work items[2]:\t\t\t\t 1024\r\n  Max work group size:\t\t\t\t 256\r\n\r\nIn particular the \"max workgroup size\" does not appear to be correct as I can execute workgroups with larger sizes just fine (tried 512)."},"comment":{"url":"https://api.github.com/repos/RadeonOpenCompute/ROCm/issues/comments/367003182","html_url":"https://github.com/RadeonOpenCompute/ROCm/issues/330#issuecomment-367003182","issue_url":"https://api.github.com/repos/RadeonOpenCompute/ROCm/issues/330","id":367003182,"user":{"login":"b-sumner","id":15801899,"avatar_url":"https://avatars1.githubusercontent.com/u/15801899?v=4","gravatar_id":"","url":"https://api.github.com/users/b-sumner","html_url":"https://github.com/b-sumner","followers_url":"https://api.github.com/users/b-sumner/followers","following_url":"https://api.github.com/users/b-sumner/following{/other_user}","gists_url":"https://api.github.com/users/b-sumner/gists{/gist_id}","starred_url":"https://api.github.com/users/b-sumner/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/b-sumner/subscriptions","organizations_url":"https://api.github.com/users/b-sumner/orgs","repos_url":"https://api.github.com/users/b-sumner/repos","events_url":"https://api.github.com/users/b-sumner/events{/privacy}","received_events_url":"https://api.github.com/users/b-sumner/received_events","type":"User","site_admin":false},"created_at":"2018-02-20T14:56:29Z","updated_at":"2018-02-20T14:56:29Z","author_association":"NONE","body":"This is the result of a number of considerations including performance and misbehaving programs that do not use the reqd_work_group_size kernel attribute and do not call clGetKernelWorkGroupInfo.  By using the kernel attribute, you can indeed have a work group \"volume\" as high as 1024, but of course this will affect the number of registers available per work-item."}}
{"actor":{"display_login":"b-sumner"}}