From: "Victor kasaksha" <>
Newsgroups: comp.soft-sys.matlab
Subject: Re: Is it a bug or what is it?
Date: Mon, 12 Oct 2009 11:31:03 +0000 (UTC)
Organization: TU Hamburg-Harburg
Lines: 17
Message-ID: <hav41n$ffi$>
References: <h9f9u0$elc$> <h9hrk6$plp$> <>
Reply-To: "Victor kasaksha" <>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Trace: 1255347063 15858 (12 Oct 2009 11:31:03 GMT)
NNTP-Posting-Date: Mon, 12 Oct 2009 11:31:03 +0000 (UTC)
X-Newsreader: MATLAB Central Newsreader 1369356
Xref: comp.soft-sys.matlab:576668

My solution to this bug:

Use some other BLAS-library as Intel MKL, what is standard used under Matlab. I tested for example with GotoBla2 and it works fine with it. The GotoBlas is almost as fast as Intel MKL, but it seems that this bug is away. 

On Linux Machines:
1. Download GotoBlas2 and install it
2. Bash terminal: export BLAS_VERSION=pathtoGotoBlas2/
3. The same terminal: matlab

You can of course set this varible in a bash script to automate your matlab call.

I think on windows machines it is the same way. You must compile gotoBlas2 for your machine and then setting the system variable BLAS_VERSION you can repair your matlab :-)

It would be interesting if somebody test it with ATLAS (parallelized)!?!

Best Regards