Web lists-archives.com

Re: RFC: Naming convention for ILP64 variant of BLAS/LAPACK




On Tue, Oct 23, 2018 at 02:12:16PM +0000, Mo Zhou wrote:
> (1) bin:libblas3  from  src:lapack
> (2) bin:libatlas3-base  from  src:atlas
> (3) bin:libopenblas-base  from  src:openblas
> (4) bin:libblis1  from  src:blis  [WIP]
> (5) bin:libmkl-rt  from  src:intel-mkl  [non-free]
> (6) bin:libnvblas9.1  from  src:nvidia-cuda-toolkit  [non-free] [2]
> 
> * I confirm these providers support 64-bit index in the API.
>   (2) (3) (4) (5)
> 
>   @Sebastien could you please confirm the status of 64-bit-index support
>   in lapack, i.e. (1) ?

Sorry, I mistyped. (2) shouldn't be there.

(2) seems not supporting 64-bit index.
    It's header uses "const int" as the type of index.
	header available in bin:libatlas-base-dev

And I took a look into the netlib blas, aka the standard BLAS
implementation and it's index type is "const int" too ...


Not every BLAS provider can provide 64-bit-index API.  It's fine if only
OpenBLAS (3), MKL (5), BLIS (4) can provide 64-bit-index API, because
they are basically the fastest cpu-based BLAS implementations publically
available.