I wonder when would they start supporting OpenCL :( I want to use my Radeon GPU
Agreed. Hardware lock-in is nasty business, and with tools like HIP it shouldn't be too difficult.
Tensorflow v1.2 released
41–45 of 45 posts
Re: Tensorflow v1.2 released
#42I wonder when would they start supporting OpenCL :( I want to use my Radeon GPU
While direct support from the creators of TF would be the beste thing, be sure to check out all the addon options, like https://github.com/hughperkins/tf-coriander
Re: Tensorflow v1.2 released
#43Note: As of version 1.2, TensorFlow no longer provides GPU support on Mac OS X.
Is there any explanation for why they decided to do this? I would imagine they just don't have the means to test on Mac anymore but I'd like to know why for sure.
The last Mac to ship with an NVidia GPU was the 2014 MBP. That was three years ago, and is starting to exit most companies' hardware refresh cycle. You can buy an external thunderbolt box and try putting an nvidia GPU in it, but the driver support isn't always functional. For an example of some of the hoops you have to go through, see: https://9to5mac.com/2017/04/11/hands-on-powering-the-macbook...
And I'm sure you can imagine the reasons a large company wouldn't set up a Hackintosh. :) The writing is on the wall for being able to maintain a reliable test cluster, at least, for now, and broken tests are very very bad for being able to develop rapidly.
Re: Tensorflow v1.2 released
#44What about Java?
Re: Tensorflow v1.2 released
#45Thank you for the release! There is an submitted issue because the Intel MKL support does not work with Mac OS X, only Linux. There should be some way of doing this manually. Any ideas?
I've managed to compile tensorflow with MKL on Mac OS X. The ingredients were roughly:
1. Download MKL from Intel's website, install to /usr/local/lib/
2. Change tensorflow's configure script to look for the downloaded library on OS X instead of just aborting.
3. Possibly change some other bazel build files to look for .dylib instead of .so files.
4. Build with extra flags to look for the appropriate libraries.
I'm not sure if all these steps are necessary but they were sufficient.
The reason I had install to /usr/local/lib/ instead of Intel's suggestion of /opt/intel/something was that, with the latter, even though I passed the appropriate directory to the linker, I think there was still some intermediate binary that wasn't seeing that path. Putting the dylibs in the default directory solved that.
I can't contribute my patch because I did this on my employer's computer and it'd be an enormous hassle to work out the licensing stuff.