[SciPy-Dev] [Numpy-discussion] ANN: Scipy 0.13.0 beta 1 release
Mon Sep 2 13:12:00 CDT 2013
On Mon, Sep 2, 2013 at 5:46 PM, Pauli Virtanen <firstname.lastname@example.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 02.09.2013 18:30, David Cournapeau kirjoitti:
> > Ok, I think the commit 5935030f8cced33e433804a21bdb15572d1d38e8 is
> > quite wrong.
> > It conflates the issue of dealing with Accelerate brokenness and
> > using g77 ABI. I would suggest reverting it for 0.13.0 (and
> > re-disable single precision), as fixing this correctly may require
> > quite some time/testing.
> I'm -1 on returning to the previous situation where many routines on
> OSX are simply broken (which was the situation previously ---
> "disabling single precision" left several things still broken). I'd
> rather just postpone the 0.13.0 release until this issue is solved
I see, I missed that it was more than just reverting to slower versions.
> Can you say what exactly is wrong -- as far as I know, Accelerate on
> OSX simply uses g77 ABI. There were some bugs previously where it in
> places did things differently, but on recent OSX releases this is no
> longer the case?
> I guess you are trying to link with MKL? In that case, I would rather
> propose restoring the previous MKL wrappers (with trivial extensions
> for the missing w* symbols).
The pb is specific to MKL, yes, but I've found a workaround: in the case of
MKL, you just need to workaround the g77 ABI of the MKL vs gfortran ABI,
but the LAPACK interface is the actual LAPACK, not CLAPACK.
So for MKL, you need non dummy wrappers iff the function returns a complex.
A dirty patch seems to confirm that this fixes the issue, I will prepare an
actual patch tomorrow,
> - --
> Pauli Virtanen
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
> -----END PGP SIGNATURE-----
> NumPy-Discussion mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SciPy-Dev