On 2022-01-12 20:00, Rebecca N. Palmer wrote:
On 12/01/2022 12:50, Drew Parsons wrote:
mesa-opencl-icd is running and passing its own tests on these arches.
What is pyopencl doing in build and tests that's different from what
mesa-opencl-icd itself does?
Probably that pyopencl's tests actually run OpenCL code and mesa's (at
least the ones that get run on a buildd) don't.
pyopencl is a package that uses OpenCL, so it makes sense to run its
tests via whatever OpenCL driver works on that hardware, which on the
buildds means pocl-opencl-icd.
mesa-opencl-icd is an OpenCL driver that requires a GPU, so if it has
tests that run OpenCL code, it probably doesn't run them on the
buildd. (It might run them on a maintainer's local machine where the
right GPU is available, like beignet-opencl-icd does.)
Thanks Rebecca.
Do we know what pyopencl would do on, say, ppc64el with mesa-opencl-icd
installed? At the moment it not even trying. Would it fail to build? If
it's only tests that would fail, then they could be skipped.
Another way to put the question, does OpenCL make any sense at all on
the failing architectures like ppc64el? (and are GPUs potentially
available for ppc64el etc, even if not available on buildds?)
What I'm wondering is whether we might want
Build-Depends: pocl-opencl-icd [amd64 arm64 armel armhf i386
hurd-i386], mesa-opencl-icd [!amd64 !arm64 !armel !armhf !i386
!hurd-i386]
