Discussion:
[PyCUDA] [PyOpenCL] New architectures for PyOpenCL in Debian
Tomasz Rybak
2017-02-11 21:01:41 UTC
Permalink
On Mon, 2016-11-21 at 22:46 -0600, Andreas Kloeckner wrote:
[ cut ]
At the same time I have a question for you Andreas. There will be
freeze of Stretch on 2017-01-05. I’d like to upload PyOpenCL and
PyCUDA
in mid-December, and those versions will be versions for Stretch.
Do
you plan new releases, or should I just take snapshots from git? 
I'll do a 2016.2.1 mid-December.
Quick update.

PyOpenCL from 2016-11-30 (commit
19015994653dffe2ee407271e19a46e1d6a62796) is in Debian testing,
for architectures amd64, arm64, armhf, i386, and amd64 and i386
for kFreeBSD. There is no release-critical errors against it
which means that this version of PyOpenCL should be in Debian Stretch.

As for PyCUDA, the version in Debian is from 2016-10-24,
commit 50457813cfe3eb359a230c4e1e546ccdef9947f8.
It's only available for amd64. I tried to build package
for ppc64el, but wasn't able to properly configure cross-compiler.

As Debian is in deep freeze now, I won't upload new versions
of packages Stretch release. Using this time I'll try to
make ppc64el PyCUDA - but it's not something I'll focus on entirely.

If you have questions or suggestions regarding packages,
please let me know.

Best regards.
--
Tomasz Rybak, Debian Maintainer <***@post.pl>
GPG: A481 824E 7DD3 9C0E C40A  488E C654 FB33 2AD5 9860
http://member.acm.org/~tomaszrybak
Andreas Kloeckner
2017-02-11 22:09:37 UTC
Permalink
Post by Tomasz Rybak
[ cut ]
At the same time I have a question for you Andreas. There will be
freeze of Stretch on 2017-01-05. I’d like to upload PyOpenCL and
PyCUDA
in mid-December, and those versions will be versions for Stretch.
Do
you plan new releases, or should I just take snapshots from git? 
I'll do a 2016.2.1 mid-December.
Quick update.
PyOpenCL from 2016-11-30 (commit
19015994653dffe2ee407271e19a46e1d6a62796) is in Debian testing,
for architectures amd64, arm64, armhf, i386, and amd64 and i386
for kFreeBSD. There is no release-critical errors against it
which means that this version of PyOpenCL should be in Debian Stretch.
As for PyCUDA, the version in Debian is from 2016-10-24,
commit 50457813cfe3eb359a230c4e1e546ccdef9947f8.
It's only available for amd64. I tried to build package
for ppc64el, but wasn't able to properly configure cross-compiler.
As Debian is in deep freeze now, I won't upload new versions
of packages Stretch release. Using this time I'll try to
make ppc64el PyCUDA - but it's not something I'll focus on entirely.
If you have questions or suggestions regarding packages,
please let me know.
That sounds great. Thank you for continuing to do an excellent job
maintaining PyOpenCL and PyCUDA in Debian!

Andreas
Vedran Miletić
2017-02-13 10:24:19 UTC
Permalink
Tomasz,

half a year ago there was one person who came to #radeon on Freenode and
talked about open source radeon driver stack almost working on ppc64 (I
have no information whether the bugs have been addressed since, but I would
presume they have). Would it be possible to provide ppc64 package for
PyOpenCL as well?

Thanks,
Vedran
Post by Andreas Kloeckner
Post by Tomasz Rybak
[ cut ]
At the same time I have a question for you Andreas. There will be
freeze of Stretch on 2017-01-05. I’d like to upload PyOpenCL and
PyCUDA
in mid-December, and those versions will be versions for Stretch.
Do
you plan new releases, or should I just take snapshots from git?
I'll do a 2016.2.1 mid-December.
Quick update.
PyOpenCL from 2016-11-30 (commit
19015994653dffe2ee407271e19a46e1d6a62796) is in Debian testing,
for architectures amd64, arm64, armhf, i386, and amd64 and i386
for kFreeBSD. There is no release-critical errors against it
which means that this version of PyOpenCL should be in Debian Stretch.
As for PyCUDA, the version in Debian is from 2016-10-24,
commit 50457813cfe3eb359a230c4e1e546ccdef9947f8.
It's only available for amd64. I tried to build package
for ppc64el, but wasn't able to properly configure cross-compiler.
As Debian is in deep freeze now, I won't upload new versions
of packages Stretch release. Using this time I'll try to
make ppc64el PyCUDA - but it's not something I'll focus on entirely.
If you have questions or suggestions regarding packages,
please let me know.
That sounds great. Thank you for continuing to do an excellent job
maintaining PyOpenCL and PyCUDA in Debian!
Andreas
_______________________________________________
PyCUDA mailing list
https://lists.tiker.net/listinfo/pycuda
--
Vedran Miletić
vedran.miletic.net
Tomasz Rybak
2017-02-13 22:01:08 UTC
Permalink
Post by Vedran Miletić
Tomasz,
half a year ago there was one person who came to #radeon on Freenode
and talked about open source radeon driver stack almost working on
ppc64 (I have no information whether the bugs have been addressed
since, but I would presume they have). Would it be possible to
provide ppc64 package for PyOpenCL as well?
In theory it's possible.
But according to Debian Policy 2.2.1 package must not require software
not present in Debian for execution.
https://www.debian.org/doc/debian-policy/ch-archive.html#s-main
Currently there is no OpenCL ICD for ppc64 in Debian - so I cannot
upload PyOpenCL for that architecture.

It would be much easier to just build PyOpenCL for all architectures,
but to be following Policy I need to manually maintain list of
architectures for which we have ICDs.

Best regards.
--
Tomasz Rybak, Debian Maintainer <***@post.pl>
GPG: A481 824E 7DD3 9C0E C40A  488E C654 FB33 2AD5 9860
http://member.acm.org/~tomaszrybak
Loading...