For me, the number one gripe with TF on Mac is the lack of OpenCL support. With the new iMac Pro coming out with an AMD Vega GPU, and the 2016 MBP having Intel graphics, I feel like it should at least be on their list of things to do. But then again, it's probably not a good idea to train on a Mac.
I run bazel build and I get this:<p>ERROR: /private/var/tmp/_bazel_qixiang/5571543a3fba611a0b0ca8efd02f3a37/external/protobuf_archive/BUILD:265:1: C++ compilation of rule '@protobuf_archive//:js_embed' failed (Exit 1).
gcc-7: error: unrecognized command line option '-fcolor-diagnostics'
gcc-7: error: unrecognized command line option '-Wthread-safety'; did you mean '-fthread-jumps'?
gcc-7: error: unrecognized command line option '-Wself-assign'; did you mean '-Wcast-align'?
Target //tensorflow/tools/pip_package:build_pip_package failed to build<p>any help?
Should also publish the benchmarks of best of class machines running TensorFlow - for Linux, Windows and Mac HWs.<p>Show Apple why they need to release better Mac Desktop/Laptop HW or risk loss the heart and mind of next generation of developers.
It's worth noting that <i>any</i> TF user (including those on NVidia Macs) can get significant speedups (20%+) by recompiling to use all the features of your CPU.<p>TF even warns you about this when you start up.