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

2018-10-23 Thread Sébastien Villemot
Le mardi 23 octobre 2018 à 14:12 +, Mo Zhou a écrit : > On Mon, Oct 22, 2018 at 07:58:38PM +0200, Bastian Blank wrote: > > On Mon, Oct 22, 2018 at 07:55:10PM +0200, Sébastien Villemot wrote: > > > For BLAS/LAPACK implementations implemented in C, like OpenBLAS, they > > > will be compiled

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

2018-10-23 Thread Sébastien Villemot
Le mardi 23 octobre 2018 à 14:17 +, Mo Zhou a écrit : > Two in the audience are object to the "-ilp64" naming convention. > Then how about this? > > src:openblas >  bin:libblas-base   (...) >  bin:libblas-dev(...) >  bin:libblas64-base (filename=libblas64.so.3, SONAME=libblas64.so.3, >   

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

2018-10-23 Thread Drew Parsons
On 2018-10-23 22:17, Mo Zhou wrote: Hi Sebastien, Two in the audience are object to the "-ilp64" naming convention. Then how about this? src:openblas bin:libblas-base (...) bin:libblas-dev(...) bin:libblas64-base (filename=libblas64.so.3, SONAME=libblas64.so.3,

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

2018-10-23 Thread Mo Zhou
On Tue, Oct 23, 2018 at 02:12:16PM +, 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)

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

2018-10-23 Thread Mo Zhou
Hi Sebastien, Two in the audience are object to the "-ilp64" naming convention. Then how about this? src:openblas bin:libblas-base (...) bin:libblas-dev(...) bin:libblas64-base (filename=libblas64.so.3, SONAME=libblas64.so.3,

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

2018-10-23 Thread Mo Zhou
On Mon, Oct 22, 2018 at 07:58:38PM +0200, Bastian Blank wrote: > On Mon, Oct 22, 2018 at 07:55:10PM +0200, Sébastien Villemot wrote: > > For BLAS/LAPACK implementations implemented in C, like OpenBLAS, they > > will be compiled using LP64, and not ILP64. Only integers exposed > > through the

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

2018-10-23 Thread Mo Zhou
On Mon, Oct 22, 2018 at 09:57:56PM +0200, Florian Weimer wrote: > > Proposal: > > > > * The "-ilp64" postfix should be appended to the SONAME of all the new > > shared objects that provide ILP64 interface. For example: > > > > libblas.so.3 (LP64) -> libblas-ilp64.so.3 (ILP64) > > > >

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

2018-10-22 Thread Florian Weimer
* Mo Zhou: > Proposal: > > * The "-ilp64" postfix should be appended to the SONAME of all the new > shared objects that provide ILP64 interface. For example: > > libblas.so.3 (LP64) -> libblas-ilp64.so.3 (ILP64) > > As a result, the same postfix should be added to the binary

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

2018-10-22 Thread Drew Parsons
On 2018-10-22 23:07, Mo Zhou wrote: Are any other packages likely to start wanting to use ILP64 ABIs? I guess it's very much an 'HPC' sort of thing at the moment. So yeah, some clarification in order I think, and an explanation of use-cases. HPC is indeed a related use case. I don't know

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

2018-10-22 Thread Bastian Blank
On Mon, Oct 22, 2018 at 07:55:10PM +0200, Sébastien Villemot wrote: > For BLAS/LAPACK implementations implemented in C, like OpenBLAS, they > will be compiled using LP64, and not ILP64. Only integers exposed > through the interface will be affected, through the use of appropriate > types. So you

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

2018-10-22 Thread Sébastien Villemot
Le lundi 22 octobre 2018 à 18:38 +0100, Simon McVittie a écrit : > On Mon, 22 Oct 2018 at 18:17:32 +0100, Ben Hutchings wrote: > > On Mon, 2018-10-22 at 15:07 +, Mo Zhou wrote: > > > Here are some references: > > > > > > 1. > > >

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

2018-10-22 Thread James Clarke
On 22 Oct 2018, at 18:17, Ben Hutchings wrote: > On Mon, 2018-10-22 at 15:07 +, Mo Zhou wrote: >> Hi Wookey and Bastian, >> >> On Sun, Oct 21, 2018 at 06:51:16PM +0100, Wookey wrote: >>> On 2018-10-21 17:16 +0200, Bastian Blank wrote: Hi On Sun, Oct 21, 2018 at 09:51:15AM

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

2018-10-22 Thread Simon McVittie
On Mon, 22 Oct 2018 at 18:17:32 +0100, Ben Hutchings wrote: > On Mon, 2018-10-22 at 15:07 +, Mo Zhou wrote: > > Here are some references: > > > > 1. > > https://software.intel.com/en-us/mkl-linux-developer-guide-using-the-ilp64-interface-vs-lp64-interface > > > >The Intel MKL ILP64

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

2018-10-22 Thread Ben Hutchings
On Mon, 2018-10-22 at 15:07 +, Mo Zhou wrote: > Hi Wookey and Bastian, > > On Sun, Oct 21, 2018 at 06:51:16PM +0100, Wookey wrote: > > On 2018-10-21 17:16 +0200, Bastian Blank wrote: > > > Hi > > > > > > On Sun, Oct 21, 2018 at 09:51:15AM +, Mo Zhou wrote: > > > > about naming convention

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

2018-10-22 Thread Mo Zhou
Hi Wookey and Bastian, On Sun, Oct 21, 2018 at 06:51:16PM +0100, Wookey wrote: > On 2018-10-21 17:16 +0200, Bastian Blank wrote: > > Hi > > > > On Sun, Oct 21, 2018 at 09:51:15AM +, Mo Zhou wrote: > > > about naming convention of SONAME and package name. > > > > > > As discussed in

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

2018-10-21 Thread Wookey
On 2018-10-21 17:16 +0200, Bastian Blank wrote: > Hi > > On Sun, Oct 21, 2018 at 09:51:15AM +, Mo Zhou wrote: > > about naming convention of SONAME and package name. > > > > As discussed in [1][2][3], Debian will need a set of ILP64[4] interface > > to BLAS/LAPACK in the future. > > Could

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

2018-10-21 Thread Bastian Blank
Hi On Sun, Oct 21, 2018 at 09:51:15AM +, Mo Zhou wrote: > about naming convention of SONAME and package name. > > As discussed in [1][2][3], Debian will need a set of ILP64[4] interface > to BLAS/LAPACK in the future. Could you please describe what you mean? All 64-bit Debian architectures