Debian Bug report logs - #875618
openblas: please enable build on s390x

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Graham Inggs <ginggs@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: openblas: please enable build on s390x

Date: Tue, 12 Sep 2017 19:28:04 +0200

Source: openblas
Version: 0.2.20+ds-1
Severity: wishlist

Hi Sébastien


From Changelog.txt in OpenBLAS 0.2.20:

IBM Z: * New target z13 with BLAS3 optimizations

I have just checked, and openblas/0.2.20-3 builds successfully on
zelenka.debian.org.
Please enable building on s390x.

Regards
Graham

Message #10 received at 875618@bugs.debian.org (full text, mbox, reply):

From: Sébastien Villemot <sebastien@debian.org>

To: Graham Inggs <ginggs@debian.org>, 875618@bugs.debian.org

Cc: debian-s390@lists.debian.org

Subject: Re: Bug#875618: openblas: please enable build on s390x

Date: Wed, 13 Sep 2017 22:11:09 +0200

[Message part 1 (text/plain, inline)]

[CC’ing the debian-s390@lists.debian.org list; s390 folks, please keep the bug
in CC on replies]

Dear Graham,

On Tue, Sep 12, 2017 at 07:28:04PM +0200, Graham Inggs wrote:
> Source: openblas
> Version: 0.2.20+ds-1
> Severity: wishlist

> From Changelog.txt in OpenBLAS 0.2.20:
> 
> IBM Z: * New target z13 with BLAS3 optimizations
> 
> I have just checked, and openblas/0.2.20-3 builds successfully on
> zelenka.debian.org.
> Please enable building on s390x.

Unfortunately it does not look that simple. OpenBLAS is optimized for z13, but
our s390x port is supposed to support all the z systems (see [1]).

In particular, the OpenBLAS build system adds the "-march=z13 -mzvector"
compilation flags. If I remove them, then the package fails to build on
zelenka: it complains about unknown assembly instructions, which are not
present on old z-systems. This is the proof that OpenBLAS cannot produce a
binary generic enough for our s390x port.

So unless I am missing something, it’s not possible to enable building for
s390x until 1) OpenBLAS supports older z-systems or 2) the hardware
requirements for the Debian s390x port are upgraded.

Best,

[1] https://www.debian.org/releases/stable/s390x/ch02s01.html.en#idm45373715987328

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄⠀⠀⠀⠀  http://www.debian.org

[signature.asc (application/pgp-signature, inline)]

Message #15 received at 875618@bugs.debian.org (full text, mbox, reply):

From: PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr>

To: Sébastien Villemot <sebastien@debian.org>, "875618@bugs.debian.org" <875618@bugs.debian.org>, Graham Inggs <ginggs@debian.org>

Cc: "debian-s390@lists.debian.org" <debian-s390@lists.debian.org>

Subject: RE:Bug#875618: openblas: please enable build on s390x

Date: Wed, 13 Sep 2017 20:33:08 +0000

Hello 

> Unfortunately it does not look that simple. OpenBLAS is optimized for z13, but
> our s390x port is supposed to support all the z systems (see [1]).

what about asking for a a z13-support package to the isa-support (source package) maintainer.
This way it could be possible to upload an optimise vesion of openblas which can install on recent enought s390x machines.

the question will be then : does the buildd support these instructions ?

Cheers

Fred

Message #20 received at 875618@bugs.debian.org (full text, mbox, reply):

From: Sébastien Villemot <sebastien@debian.org>

To: PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr>

Cc: "875618@bugs.debian.org" <875618@bugs.debian.org>, Graham Inggs <ginggs@debian.org>, "debian-s390@lists.debian.org" <debian-s390@lists.debian.org>

Subject: Re: Bug#875618: openblas: please enable build on s390x

Date: Thu, 14 Sep 2017 09:58:05 +0200

[Message part 1 (text/plain, inline)]

On Wed, Sep 13, 2017 at 08:33:08PM +0000, PICCA Frederic-Emmanuel wrote:
> Hello 
> 
> > Unfortunately it does not look that simple. OpenBLAS is optimized for z13, but
> > our s390x port is supposed to support all the z systems (see [1]).
> 
> what about asking for a a z13-support package to the isa-support (source
> package) maintainer. This way it could be possible to upload an optimise
> vesion of openblas which can install on recent enought s390x machines.

I am not totally convinced by this solution. If we adopt it, somebody who
installs e.g. octave on an old system-z machine will be hit by a failure in the
dpkg installation process, which needs manual intervention. This is likely to
generate problems in automated installers (and also confuse and annoy system
admins).

> the question will be then : does the buildd support these instructions ?

I leave that to the s390 porters to answer.

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄⠀⠀⠀⠀  http://www.debian.org

[signature.asc (application/pgp-signature, inline)]

Message #25 received at 875618@bugs.debian.org (full text, mbox, reply):

From: Christian Borntraeger <borntraeger@de.ibm.com>

To: Sébastien Villemot <sebastien@debian.org>, PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr>

Cc: "875618@bugs.debian.org" <875618@bugs.debian.org>, Graham Inggs <ginggs@debian.org>, "debian-s390@lists.debian.org" <debian-s390@lists.debian.org>

Subject: Re: Bug#875618: openblas: please enable build on s390x

Date: Thu, 14 Sep 2017 12:34:34 +0200

On 09/14/2017 09:58 AM, Sébastien Villemot wrote:
> On Wed, Sep 13, 2017 at 08:33:08PM +0000, PICCA Frederic-Emmanuel wrote:
>> Hello 
>>
>>> Unfortunately it does not look that simple. OpenBLAS is optimized for z13, but
>>> our s390x port is supposed to support all the z systems (see [1]).
>>
>> what about asking for a a z13-support package to the isa-support (source
>> package) maintainer. This way it could be possible to upload an optimise
>> vesion of openblas which can install on recent enought s390x machines.
> 
> I am not totally convinced by this solution. If we adopt it, somebody who
> installs e.g. octave on an old system-z machine will be hit by a failure in the
> dpkg installation process, which needs manual intervention. This is likely to
> generate problems in automated installers (and also confuse and annoy system
> admins).
> 
>> the question will be then : does the buildd support these instructions ?
> 
> I leave that to the s390 porters to answer.

FWIW, some years ago I did the atlas port for s390x. For dynamic linking the atlas
build/package process did support the exploitation of ELF HW_CAPS. So you could 
build a z900 (generic) and a z13 variant which is then picked by the linker at 
runtime. No idea if openblas allows the same. Of course the static variant (.a) 
must be the generic one.

Christian

Message #30 received at 875618@bugs.debian.org (full text, mbox, reply):

From: Sébastien Villemot <sebastien@debian.org>

To: Christian Borntraeger <borntraeger@de.ibm.com>

Cc: PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr>, "875618@bugs.debian.org" <875618@bugs.debian.org>, Graham Inggs <ginggs@debian.org>, "debian-s390@lists.debian.org" <debian-s390@lists.debian.org>

Subject: Re: Bug#875618: openblas: please enable build on s390x

Date: Mon, 18 Sep 2017 13:56:23 +0200

[Message part 1 (text/plain, inline)]

Control: tags -1 upstream
Control: forwarded -1 https://github.com/xianyi/OpenBLAS/issues/1307

On Thu, Sep 14, 2017 at 12:34:34PM +0200, Christian Borntraeger wrote:
> On 09/14/2017 09:58 AM, Sébastien Villemot wrote:
> > On Wed, Sep 13, 2017 at 08:33:08PM +0000, PICCA Frederic-Emmanuel wrote:
> >>> Unfortunately it does not look that simple. OpenBLAS is optimized for z13, but
> >>> our s390x port is supposed to support all the z systems (see [1]).
> >>
> >> what about asking for a a z13-support package to the isa-support (source
> >> package) maintainer. This way it could be possible to upload an optimise
> >> vesion of openblas which can install on recent enought s390x machines.
> > 
> > I am not totally convinced by this solution. If we adopt it, somebody who
> > installs e.g. octave on an old system-z machine will be hit by a failure in the
> > dpkg installation process, which needs manual intervention. This is likely to
> > generate problems in automated installers (and also confuse and annoy system
> > admins).
> > 
> >> the question will be then : does the buildd support these instructions ?
> > 
> > I leave that to the s390 porters to answer.
> 
> FWIW, some years ago I did the atlas port for s390x. For dynamic linking the atlas
> build/package process did support the exploitation of ELF HW_CAPS. So you could 
> build a z900 (generic) and a z13 variant which is then picked by the linker at 
> runtime. No idea if openblas allows the same. Of course the static variant (.a) 
> must be the generic one.

Thanks for your feedback. I have opened a request upstream about the need for a
z900 kernel, and for a dynamic selection between the z900 and z13 kernels
(as OpenBLAS currently does on x86).

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄⠀⠀⠀⠀  http://www.debian.org

[signature.asc (application/pgp-signature, inline)]

Message #39 received at 875618@bugs.debian.org (full text, mbox, reply):

From: Sébastien Villemot <sebastien@debian.org>

To: 875618@bugs.debian.org

Cc: Christian Borntraeger <borntraeger@de.ibm.com>, PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr>, debian-s390@lists.debian.org, Graham Inggs <ginggs@debian.org>

Subject: Re: Bug#875618: openblas: please enable build on s390x

Date: Tue, 19 Sep 2017 12:42:46 +0200

[Message part 1 (text/plain, inline)]

Control: tags -1 = pending
Control: notforwarded -1

On Mon, Sep 18, 2017 at 01:56:23PM +0200, Sébastien Villemot wrote:
> On Thu, Sep 14, 2017 at 12:34:34PM +0200, Christian Borntraeger wrote:
> > On 09/14/2017 09:58 AM, Sébastien Villemot wrote:
> > > On Wed, Sep 13, 2017 at 08:33:08PM +0000, PICCA Frederic-Emmanuel wrote:
> > >>> Unfortunately it does not look that simple. OpenBLAS is optimized for z13, but
> > >>> our s390x port is supposed to support all the z systems (see [1]).
> > >>
> > >> what about asking for a a z13-support package to the isa-support (source
> > >> package) maintainer. This way it could be possible to upload an optimise
> > >> vesion of openblas which can install on recent enought s390x machines.
> > > 
> > > I am not totally convinced by this solution. If we adopt it, somebody who
> > > installs e.g. octave on an old system-z machine will be hit by a failure in the
> > > dpkg installation process, which needs manual intervention. This is likely to
> > > generate problems in automated installers (and also confuse and annoy system
> > > admins).
> > > 
> > >> the question will be then : does the buildd support these instructions ?
> > > 
> > > I leave that to the s390 porters to answer.
> > 
> > FWIW, some years ago I did the atlas port for s390x. For dynamic linking the atlas
> > build/package process did support the exploitation of ELF HW_CAPS. So you could 
> > build a z900 (generic) and a z13 variant which is then picked by the linker at 
> > runtime. No idea if openblas allows the same. Of course the static variant (.a) 
> > must be the generic one.
> 
> Thanks for your feedback. I have opened a request upstream about the need for a
> z900 kernel, and for a dynamic selection between the z900 and z13 kernels
> (as OpenBLAS currently does on x86).

It turns out that there is already a support for generic System z, I had
overlooked that.

I have therefore pushed a changeset that builds a generic s390x binary.

However, upstream does not currently provide runtime detection, so owners of a
z13 system will have to recompile locally (as explained in README.Debian) in
order to get the best out of OpenBLAS (note that this is the same situation as
all the non-x86 archs).

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄⠀⠀⠀⠀  http://www.debian.org

[signature.asc (application/pgp-signature, inline)]

Message #48 received at 875618-close@bugs.debian.org (full text, mbox, reply):

From: Sébastien Villemot <sebastien@debian.org>

To: 875618-close@bugs.debian.org

Subject: Bug#875618: fixed in openblas 0.2.20+ds-4

Date: Tue, 19 Sep 2017 13:20:57 +0000

Source: openblas
Source-Version: 0.2.20+ds-4

We believe that the bug you reported is fixed in the latest version of
openblas, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 875618@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sébastien Villemot <sebastien@debian.org> (supplier of updated openblas package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 19 Sep 2017 14:51:23 +0200
Source: openblas
Binary: libopenblas-base libopenblas-dev
Architecture: source
Version: 0.2.20+ds-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team <debian-science-maintainers@lists.alioth.debian.org>
Changed-By: Sébastien Villemot <sebastien@debian.org>
Description:
 libopenblas-base - Optimized BLAS (linear algebra) library (shared library)
 libopenblas-dev - Optimized BLAS (linear algebra) library (development files)
Closes: 875618
Changes:
 openblas (0.2.20+ds-4) unstable; urgency=medium
 .
   * Add support for s390x.
     New patch force-zarch.patch introduced to force the generic build.
     (Closes: #875618)
   * Enforce TARGET=POWER6 on ppc64, to avoid FTBFS on some buildds.
   * Drop obsolete code for -dbgsym migration.
Checksums-Sha1:
 d6dd8abaaed1f078f86d21282d01677c18577aa3 2453 openblas_0.2.20+ds-4.dsc
 dd8cf0d419fa0c6526e1573e89c82b212889a2ac 16864 openblas_0.2.20+ds-4.debian.tar.xz
 828cb8896db1e82608911263cadb45c7839a4b14 6105 openblas_0.2.20+ds-4_amd64.buildinfo
Checksums-Sha256:
 416ba81b74dc6d4eb896335d8fcfaf97a36d1508266d99d5634858dbd963edaf 2453 openblas_0.2.20+ds-4.dsc
 1495b32e62af4e8b380cd1a5abd05d454bc6527414d0a788070868fa3f062cdf 16864 openblas_0.2.20+ds-4.debian.tar.xz
 6587b430683656f7eee27ecea8d2f267420fdc7371bdf379bc17676cb24caa23 6105 openblas_0.2.20+ds-4_amd64.buildinfo
Files:
 027ec976c3d47c3e12093139f1ce033d 2453 devel optional openblas_0.2.20+ds-4.dsc
 f27f2e69e548da223de642d27ac50029 16864 devel optional openblas_0.2.20+ds-4.debian.tar.xz
 fcc215cfc942f1eec2d15c19f74dc385 6105 devel optional openblas_0.2.20+ds-4_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAlnBFVUACgkQLOzpNQ7O
vkqOTw//ar64k3y4wUDaqKzNo5S7YRejcb2MCK7ZE46N6AGNCWhT97wmvEigDzTO
hENkiCCtgyp/VnkYtUBfcrpl25ARLC27G/+YE1H0Jxc4AiZoR0h26ZMGGY5bFSDB
Ys0RSAwsAk31wz9VdVNNfndys4uw476PBX/8it/73O8E/p0xUznJmh6wV/8UwsnW
zq69tFUPd55KVPnq2mq+1ZFTgrBwvnm7SeVKpvRUf2tMAF/eOX29eJ53kN5s/fpr
Xj+5rwHwIVOEVkhBRDUw8BqPzJ2DSy0iBSVfDFA7IJelB1jgPJoUbwEMkGMU0+yH
ALqNYVWybCt5Yx8yOnHiM/0ohhziTggQQDdqFQE4AQ0byxFhfnEoAkmGgv6KIzSy
EXlcBrEgo4XdEGaf1T35WaR8A16awkwuFlxn1RBJABsYild5VjCjnkTj3EyEWyhv
TVgcLc6EtpCszEt9MSvFa7/VpILhQpIZdgweQ9xvrUPSoOVQeO/7r75x7NPGnp1N
7oziA3/ymiO1fQluWa2zPls/ZS4SwBfe9rX3YTHon7j/URLtgW5mreXNY5r3lT9j
YAwfWwS7y/HYkn8C8fIqwUnKSN4N2o9MBJyJQetlk0rN4tTsdVlwHAuKc3xtUivc
qjyTKyDKVpIF6EGhDXW6Rj+WyUgwzK7+JI8znAMH7IQX9S1Nbp4=
=v2Fs
-----END PGP SIGNATURE-----

Message #53 received at 875618@bugs.debian.org (full text, mbox, reply):

From: Graham Inggs <ginggs@debian.org>

To: 875618@bugs.debian.org, Sébastien Villemot <sebastien@debian.org>

Subject: Re: Bug#875618 closed by Sébastien Villemot <sebastien@debian.org> (Bug#875618: fixed in openblas 0.2.20+ds-4)

Date: Tue, 19 Sep 2017 18:29:43 +0200

Thanks Sébastien!  I'm sorry it turned out not to be as simple as I 
originally thought.

Send a report that this bug log contains spam.