On 02/02/2020 22.38, Rebecca N. Palmer wrote:
On 01/02/2020 13:32, Andreas Beckmann wrote:
Is this issue still reproducible with recent versions of pocl?
Yes, and if anything it's worse in that it can now be silently wrong
answers not just crashes.
Two years later I ask again. ;-)
The bug
On 01/02/2020 13:32, Andreas Beckmann wrote:
Is this issue still reproducible with recent versions of pocl?
Yes, and if anything it's worse in that it can now be silently wrong
answers not just crashes.
(Each example output below is from a separate run of the test suite,
after reverting
On 26/01/2019 11.16, Rebecca N. Palmer wrote:
> libgpuarray's test_ger (DEVICE=opencl0:0 POCL_KERNEL_CACHE=0 nosetests3
> -v pygpu.tests.test_blas:test_ger, requires python3-pygpu, python3-nose,
> python3-scipy, ocl-icd-opencl-dev, libclblas-dev) crashes with memory
> corruption errors (e.g.
https://github.com/pocl/pocl/issues/691
On 2019-01-31 15:02, Michal Babej wrote:
> one idea worth trying would be to run that program in OCLgrind. If
OCLgrind reports memory access errors, the error is likely in the
program, otherwise it's likely in pocl.
Package: libclblas2,libpocl2
Version: 2.12-1,1.2-3
(and also 1.2-2, but the below is from -3)
libgpuarray's test_ger (DEVICE=opencl0:0 POCL_KERNEL_CACHE=0 nosetests3
-v pygpu.tests.test_blas:test_ger, requires python3-pygpu, python3-nose,
python3-scipy, ocl-icd-opencl-dev, libclblas-dev)
5 matches
Mail list logo