Displaying 3 results from an estimated 3 matches for "cblas_nam".
Did you mean:
cblas_name
2020 Jul 15
2
Openblas?
...G?ran,
>
> This is not an easy email to reply to because it _contains nothing
> reproducible_.
Thanks Dirk,
Sorry about that, but my real question was (see below): "Is the problem
that openblas uses C versions of blas?" That is, do I need to change
F77_CALL(name)(...);
to
cblas_name(...);
everywhere? And if so, is this really a good idea with old code?
I'll try to extract a reproducible example from the package (eha) where
I run it.
G?ran
>
> On 15 July 2020 at 13:24, G?ran Brostr?m wrote:
> | Hello,
> |
> | I thought that I should try openblas when b...
2020 Jul 15
0
Openblas?
...is not an easy email to reply to because it _contains nothing
| > reproducible_.
|
| Thanks Dirk,
|
| Sorry about that, but my real question was (see below): "Is the problem
| that openblas uses C versions of blas?" That is, do I need to change
|
| F77_CALL(name)(...);
|
| to
|
| cblas_name(...);
|
| everywhere? And if so, is this really a good idea with old code?
I don't think so. At the end of the day it comes from "higher up" (say,
crossprod()) and is just passed down.
Remember, at the end it's all assembler :)
| I'll try to extract a reproducible example...
2020 Jul 15
2
Openblas?
Hello,
I thought that I should try openblas when building a CRAN package
containing lots of old (twentieth century) C-code with frequent calls to
blas and lapack routines. I have the following options on my Ubuntu
20.04 machine:
Selection Path Priority Status
------------------------------------------------------------
* 0