[Numpy-discussion] Default builds of OpenBLAS development branch are now fork safe

Carl Kleffner cmkleffner at gmail.com
Sun Apr 6 15:47:43 EDT 2014


MKL BLAS LAPACK has issues as well:
http://software.intel.com/en-us/articles/intel-mkl-110-bug-fixes .
In case of OpenBLAS or GOTOBLAS what precisly is the problem you identify
as showstopper?

Regards

Carl




2014-04-06 20:59 GMT+02:00 Matthew Brett <matthew.brett at gmail.com>:

> Hi,
>
> On Sun, Apr 6, 2014 at 11:47 AM, Sturla Molden <sturla.molden at gmail.com>
> wrote:
> > Matthew Brett <matthew.brett at gmail.com> wrote:
> >
> >> Julian - do you have any opinion on using gotoBLAS instead of OpenBLAS
> >> for the Windows binaries?
> >
> > That is basically OpenBLAS too, except with more bugs and no AVX support.
>
> I know that OpenBLAS is a fork of gotoBLAS2, but you said in another
> thread that gotoBLAS2 was 'rock-solid'.  If the bugs in gotoBLAS2 do
> not in practice arise for default Windows builds, then it could be a
> good option until OpenBLAS is more mature.
>
> Put another way - does anyone know what bugs in gotoBLAS2 do arise for
> Windows / Intel builds?
>
> Cheers,
>
> Matthew
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20140406/d2508f47/attachment.html>


More information about the NumPy-Discussion mailing list