PyOpenCL November 2015

pyopencl@tiker.net

13 participants
16 discussions

Re: [PyOpenCL] Is it possible to use CodeXL to debug PyOpenCL project

by Dude Dudish

Yu, All, yes, there's a way. CodeXL (AMD) tool is capable of debugging single-step source-level wise through ur kernel code at runtime, however, while working relatively straightforward for CPUs certain prerequisites apply to cases of using GPUs (primarily regarding the HW). Pls check out Link AND ATTACHMENT (pdf) on that site: http://wiki.tiker.net/PyOpenCL/Debugging I uploaded text and pdf including the screenshot and config instructions lil while ago. Joyfully looking forward to some other user-experiences.... :-) BR from Frankfurt, Kai On Thu, Nov 19, 2015 at 9:29 AM, Yu Yang <yy2012cn(a)gmail.com> wrote: > PyOpenCL is very convenient, but it seems that CodeXL can't debug PyOpenCL > project, any solutions? thx > > _______________________________________________ > PyOpenCL mailing list > PyOpenCL(a)tiker.net > http://lists.tiker.net/listinfo/pyopencl > >

4 years, 11 months

Is it possible to use CodeXL to debug PyOpenCL project

by Yu Yang

PyOpenCL is very convenient, but it seems that CodeXL can't debug PyOpenCL project, any solutions? thx

4 years, 11 months

documentation on create_sub_devices

by Sven Warris

Dear all, The current documentation on cl device fission states that create_sub_devices is a method of Context, but it is a method of Device. In my code this works out as: self.device = self.device.create_sub_devices([cl.device_partition_property.EQUALLY,int(number_of_compute_units)])[int(sub_device)] Cheers, Sven

4 years, 11 months

Re: [PyOpenCL] [pyopencl 2015.2] NotImplementedError: global_work_offset

by Andreas Kloeckner

Guilherme Gonçalves Ferrari <gg.ferrari(a)gmail.com> writes: > Hi Andreas, > sorry for the delay! > yes, it works fine for me. > please go ahead and push it to 2015.2.1. Thanks for getting back to me. 2015.2.1 is out. Andreas

4 years, 11 months

Re: [PyOpenCL] [pyopencl 2015.2] NotImplementedError: global_work_offset

by Andreas Kloeckner

Guilherme Gonçalves Ferrari <gg.ferrari(a)gmail.com> writes: > Hi, > I just updated to 2015.2 version and got this error when trying to run my > code: > > Traceback (most recent call last): > ... > File > "/home/guilherme/Modelos/python/conda/miniconda/envs/py27/lib/python2.7/site-packages/pyopencl/cffi_cl.py", > line 1191, in enqueue_nd_range_kernel > raise NotImplementedError("global_work_offset") > NotImplementedError: global_work_offset > > would it be possible to fix this in the next release? For now, I'm going to > downgrade to 2015.1, which works fine... Thanks for the report! Should be fixed in git. Could you try that and let me know if it works for you? If so, I'll push out 2015.1.1. Andreas

4 years, 11 months

[pyopencl 2015.2] NotImplementedError: global_work_offset

by Guilherme Gonçalves Ferrari

Hi, I just updated to 2015.2 version and got this error when trying to run my code: Traceback (most recent call last): ... File "/home/guilherme/Modelos/python/conda/miniconda/envs/py27/lib/python2.7/site-packages/pyopencl/cffi_cl.py", line 1191, in enqueue_nd_range_kernel raise NotImplementedError("global_work_offset") NotImplementedError: global_work_offset would it be possible to fix this in the next release? For now, I'm going to downgrade to 2015.1, which works fine... Thanks, Guilherme

4 years, 11 months

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

PyOpenCL November 2015