[SciPy-Dev] disabling Accelerate on OS X
Wed Jun 12 10:10:54 CDT 2013
Anybody out there at WWDC who could ask the Apple engineers?
I am trying to build SciPy and NumPy on 10.9 right now, will let you know
if I get anywhere.
On Wed, Jun 12, 2013 at 1:24 AM, Ralf Gommers <firstname.lastname@example.org>wrote:
> On Wed, Jun 12, 2013 at 1:50 AM, Jack Howarth <email@example.com>wrote:
>> On Tue, Jun 11, 2013 at 08:34:31AM +0200, Ralf Gommers wrote:
>> > Hi,
>> > Given the issues we've been having with Accelerate on OS X 10.7 and
>> > we plan to disable support for it completely in scipy (and numpy, will
>> > bring that up on numpy-discussion later) before the next release.
>> > Background:
>> > https://github.com/scipy/scipy/issues/2248
>> > https://github.com/scipy/scipy/issues/2547
>> > This will make compiling on OS X harder, but we can't leave
>> > giving incorrect results (and ~70 test errors) hang around forever, so
>> > have to do something. We'll do some testing and write up a guide for
>> how to
>> > build against other BLAS/LAPACK implementations. Homebrew already
>> > OpenBLAS, so that's a good option for who doesn't want to go through
>> > compiling their own libraries.
>> > Ralf
>> Has any attempt been made to open radar reports for these specific
>> in recent Accelerate framework releases? Also are these failures limited
>> to single
>> precision math? Lastly, were these failures introduced with Mac OS X
>> 10.7? If so,
>> perhaps they are related to the fact that llvm's compiler-rt was being
>> used to
>> build the Accelerate framework rather than the older libgcc derived math
>> If a few standalone test cases could be crafted for these Accelerate
>> detected by scipy, we might well be able to get those fixed for Mac OS X
> In 10.7 it looked like it was only single precision, but for 10.8 there
> are also double precision tests that have started failing. llvm-gcc indeed
> caused additional issues as well, could be a root cause. For 10.7 Clang and
> plain gcc worked fine (except for the Accelerate bugs) while llvm-gcc was
> crashing all over the place.
> I know there was a bug filed for SDOT in 2009 already,
> http://www.macresearch.org/lapackblas-fortran-106#comment-17216, but it
> hasn't been fixed. The Apple bug tracker isn't public, so I don't know what
> else has been filed.
> Getting any fixes for 10.9 that are not already in sounds extremely
> SciPy-Dev mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SciPy-Dev