Hi:
        I do not how the pocl add the definition of   _local_id_x , _local_id_y 
... to the final shared object. Can you show me where or how.
        I check the code that _local_id_x _local_id_y variable  is external, 
not  the definition.

BR
Owen

-----邮件原件-----
发件人: Pekka Jääskeläinen [mailto:[email protected]] 
发送时间: 2017年11月16日 15:30
收件人: Wuweijia <[email protected]>; Portable Computing Language development 
discussion <[email protected]>
抄送: Fanbohao <[email protected]>
主题: Re: 答复: [pocl-devel] [POCL_DBG] How to debug the cl file.

Hi,

This would be an extremely useful feature, but I don't know of anyone working 
on it at the moment. Contributions welcome.

BR,
Pekka

On 16.11.2017 02:43, Wuweijia wrote:
> hi
>       Is there any milestone about how to release that function?
> BR
> Owen
> 
> -----邮件原件-----
> 发件人: Pekka Jääskeläinen [mailto:[email protected]]
> 发送时间: 2017年11月15日 19:32
> 收件人: Portable Computing Language development discussion 
> <[email protected]>; Wuweijia <[email protected]>
> 抄送: Fanbohao <[email protected]>
> 主题: Re: [pocl-devel] [POCL_DBG] How to debug the cl file.
> 
> Hi,
> 
> I think the debug info generation and preservation across WGF passes is 
> unfinished.
> 
> I typically end up using printf() when debugging kernel code, and look at the 
> disassembly in gdb, which usually helps to spot the kernel lines where the 
> crash happens.
> 
> On 10.11.2017 10:33, Wuweijia wrote:
>>               I write cl file , and ran it with the pocl in arm64 
>> server, compilation is ok.  In the running  there is some bug in the 
>> cl file, and application crash in the cl file . How can I debug the cl file 
>> with gdb.
>>
>>               I think the pocl compile the cl file with some 
>> optimized options, no debug info.  Show the gdb can not show me the 
>> callstack where cl file crash.
> 
> --
> Pekka
> 

--
Pekka
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
pocl-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pocl-devel

Reply via email to