Subject: Re: [ublas] [bindings][blas] Included CBLAS support
From: Rutger ter Borg (rutger_at_[hidden])
Date: 2010-01-08 09:32:55
Thomas Klimpel wrote:
> I should be able to help... (I'm sorry that I haven't found time earlier.)
> I updated the old regression tests to work with the automatically
> generated version of the bindings from 14. October 2009. This also means
> that the updated regression tests don't work with the new traits system
> yet. However, I hope it won't be too difficult to update them to the new
> traits system now (and perhaps we will find and fix some bugs of the new
> traits system on the way).
Thanks Thomas. I've worked on the LAPACK regression suite, and over 70%
passes now using the latest generated bindings and traits.
Any hints on what to do with this lapack band storage requirement for e.g.
gbtrs/gbsv? It kind of doesn't fit anything, it's like a workspace inside a
>> To unify the interface, the character arguments to BLAS calls are
>> translated to cblas enums, matrix orientation is assumed to be column
>> major by default. IMHO, this makes the ATLAS bindings obsolete.
> For the moment, I just checked that the ATLAS, umfpack and mumps
> regression tests pass again for me. So I haven't updated the 36 ATLAS
> regression tests to the automatically generated version of the bindings.
> Having automatically generated ATLAS bindings would certainly be nice, and
> the cblas part is definitively the bulk of them.
Meanwhile, the BLAS generator produces high quality bindings. This should be
a matter of defining BOOST_NUMERIC_BINDINGS_BLAS_CBLAS and replacing atlas::
with blas::. To build against ATLAS, you probably include cblas.h, which is
used to generate the CBLAS bindings. I.e., ATLAS doesn't define a new API,
it implements one (well, two actually, it also provides the fortran one). Or
do you mean CLAPACK, or some other part?