5 ms·
Apple has the Accelerate.framework already, which is hand-tuned per chip-type, and is what most of the libraries call into. I’d imagine a lot of work will have
by spacedcowboy 6y ago
Apple has the Accelerate.framework already, which is hand-tuned per chip-type, and is what most of the libraries call into. I’d imagine a lot of work will have been done to make that as seamless as possible on the new chips.
It’s also kind of useful for a a framework team to be able to call up the guy designing the next cou and say that “this bit here is a bottleneck, what can you do for that?”...
- Someone 6y agoMoreover, BLAS is part of the Accelerate framework (https://developer.apple.com/documentation/accelerate https://developer.apple.com/documentation/accelerate), so if your code targets that, no porting is needed.
- physicsguy 6y agoYou still need to recompile and relink. And it's not that simple, Apple's implementation of LAPACK is well out of date for e.g. - it dates back to 2009.
- physicsguy 6y agoAccelerate is barely used on Mac for scientific stuff in my experience. People tend to use Intel MKL - see for e.g. the Anaconda Python distribution - all of the NumPy/SciPy libs are linked against MKL. SciPy actually went as far as dropping Accelerate as a supported BLAS implementation in 2018. https://github.com/scipy/scipy/wiki/Dropping-support-for-Accelerate https://github.com/scipy/scipy/wiki/Dropping-support-for-Acc...