metal3d commented on issue #621: Support for other Device Types, OpenCL AMD GPU URL: https://github.com/apache/incubator-mxnet/issues/621#issuecomment-582041173 @leezu excuse me, but your remark seems to not be serious. "Contributions welcome" is like to say "do it if you're so strong". The core of kernel compilation for machine learning in that kind of framework is "central", that's something that is chosen at the beginning and along the development process. Contribution by "one guy external to the project" is not possible for that. If I want to work on that: - I need to learn OpenCL in detail - I need to onboard MxNet framework development - I need a team - and a lot of time The problem is that we are asking for OpenCL in a lot of frameworks since **months, or years** - and there is _rarely_ some answers about: - Why to choose CUDA that is closed, proprietary and has got a cost for hardware, working on closed driver, with libraries you can download after registration on NVidia website - Why to not give any news on OpenCL integration possibilities, only some "news" We don't force authors to use OpenCL, we only wonder why there is nothing done in that direction. Look at that issue, it is opened since 4 years. 4 years ! Look at the question on TF: https://github.com/tensorflow/tensorflow/issues/22 4 years too. As for Mxet, we never had "clear" answer. No track of something that can explain why and/or how to fix that need. If someone is working on... Worst: TF has only one active project to compile it with SYSCL. You need to register your user, and try a long compilation that fails 90% of time. So, sorry if my comment, question, and answers seem to be "aggressive" but 4 years is a bit long without any clear answer like "we won't do that", or "we cannot", or "we will try" and/or why it is not in the way. So, "contributions welcome"... please... it's like if you're telling to someone in the street "sorry, what time is it" for 5 hours... and after that the man answer "go buy a watch"
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
