[Numpy-discussion] Dropping support for Accelerate/veclib?
Tue Jun 11 07:09:09 CDT 2013
On Tue, Jun 11, 2013 at 5:17 AM, Pauli Virtanen <firstname.lastname@example.org> wrote:
> David Cournapeau <cournape <at> gmail.com> writes:
>> What is the default ABI used on homebrew ? I think we should just
>> follow that, given that Apple cannot figure it out.
> I think for Scipy homebrew uses the Gfortran ABI:
> But that's probably the wrong thing to do, it doesn't work:
> For Octave, they have -ff2c:
> A third option (maybe the best one) could be to add an ABI check
> to numpy.distutils BLAS/LAPACK detection --- compile a small test
> program that checks SDOT/CDOTU/DDOT etc., and refuse to use the
> BLAS/LAPACK libraries if they give incorrect results. After that,
> we can also remove the sdot/cdotu wrappers.
> This approach is used by Octave.
> This leaves the problem of dealing with Fortran ABI to those in
> charge of the build environment, e.g., macports, Enthought, ...,
> who are also in the best position to pick the correct solution
> per each platform supported.
> AFAIK custom compiler flags can be injected via FOPT/FFLAGS/LDFLAGS,
> so doing something like
> export FOPT="-ff2c"
> export LDFLAGS="-ldotwrp -lblas"
> works? This makes things a bit more complicated to the builder, an
> issue that can be solved with documentation, and keeping that up to
> date is easier than hardcoding stuff into numpy.distutils.
What will be the performance drop for the default OSX installer
version of numpy, if we drop Accelerate / veclib support?
More information about the NumPy-Discussion