Control: forwarded -1 https://github.com/pocl/pocl/issues/1176
@elbrus: Why does britney try to migrate clinfo together with pocl?
IMO clinfo should be able to migrate on its own without causing new
regressions in testing. It does not have any (transitive) dependency on
pocl.
On Thu, 16 Feb 2023 21:46:31 +0000 "Rebecca N. Palmer"
<rebecca_pal...@zoho.com> wrote:
The trigger is probably pocl, not clinfo. I don't yet know whether the
bug is in pocl or libgpuarray.
or llvm-15
pocl/sid is built against llvm-15, pocl/testing against llvm-14
This also causes a test regression in pyopencl due to numerical
differences (#1030298). This was attempted to be fixed in pyopencl
upstream by requiring the numerical difference to be below some
tolerance level instead of requiring equality, but the numerical delta
is too large to hide behind that ...
I'm currently trying to debug the code generation delta between llvm-14
and llvm-15 ...
There could still be a bug in libgpuarray if the failing test is too
strict by requiring equality of some floating point computations. (Not
checked.)
Andreas
