[SciPy-Dev] Use vecLibFort instead of Accelerate?

Matthew Brett matthew.brett at gmail.com
Sat Oct 11 17:56:54 EDT 2014


On Sat, Oct 11, 2014 at 2:04 PM, Sturla Molden <sturla.molden at gmail.com> wrote:
> Matthew Brett <matthew.brett at gmail.com> wrote:
>
>> 1) Pull in our own versions of the sgemv workaround in scipy;
>> 2) Use vecLibFort to replace our own Accelerate wrappers.
>>
>> Having the Accelerate wrappers and fixes go in one place seems like a
>> good idea in general, but I know nothing about the issues, I'm afraid.
>
> A global fix would solve the problem everywhere. Probably easier to
> maintain.
>
>
>> Sturla - I saw you asking the author of vecLibFort about a cblas_sgemv
>> fix at [1] - would the plan be to use vecLibFort in numpy also?
>
> That was why I asked. My current fix for NumPy adds some minor changes the
> dotblas C code. I would rather avoid this.

Would both numpy and scipy need a copy of vecLibFort at build time?

Thanks for following up on this,

Matthew



More information about the SciPy-Dev mailing list