From: Piotr Luszczek
Date: Mon, 08 Jan 2007 10:30:33 -0500
thank you for your input. We're working on CLAPACK 3.1 right now.
I'm guessing that some unnecessary 'static' attributes might have
caused the trouble.
Could you please let me know more details about your problems?
Which routines are you using? What system is it on? What compiler?
Klaas Vantournhout wrote, On 01/06/2007 09:45 AM:
Dear mighty developers of LAPACK and CLAPACK,
In the past year I started to use CLAPACK and was flabbergasted by its
power. At the current time I try to implement openmp directives in my
code to parallelise some procedures and found out that at the usage of
some CLAPACK functions created severe memory problems. These got solved
when stating the CLAPACK functions as critical, so that they ran one at
Although the critical pragma directive is a solution, it is not
preferred. Simultaneous runs of CLAPACK functions would give me the
Lately I read that LAPACK 3.1 was released and that it got threadsafe
implementations into it. Therefore I assume that CLAPACK 3.0 is not
threadsafe and is the cause of the above mentioned problem. Is this
correct? If so, are there plans to create CLAPACK 3.1, or are there
other solutions to my problem.
With kind regards,