[llvm-dev] Debug info for CUDA code

[Valentin Churavy via llvm-dev]

If you only need line-information that information is already present and
should be useful. As long as you set `-g` you should get some and there is
a flag to turn ptxas optimisation off to preserve as much debuginformation
as possible.

You then can also run your code under cuda-memcheck

On Fri, Dec 14, 2018, 16:55 treinz <treinz at 163.com wrote:

> Are you planning to release this as soon as it's ready or you want to make
> it into a major release? Is it possible to let me know (maybe by replying
> to this thread) once the code is ready? I know sometimes it takes a while
> to get things in the major release. I greatly appreciate your work on this!
>
> Thanks,
> Char
>
> 在 2018-12-15 05:19:50，"Alexey Bataev" <a.bataev at outlook.com> 写道：
>
> Hi Char, sorry, you need to wait a little bit. It is almost ready, but not
> yet. For now, use nvcc if you need debug info for Cuda.
>
> -------------
> Best regards,
> Alexey Bataev
>
> 14.12.2018 14:33, treinz пишет:
>
> Hi Alex, Eric and Valentin,
>
> Thanks for the information. I don't mean to push this but I'm in desperate
> need of debugging some cuda code. I'm not familiar with the llvm internal
> but it sounds like there's at least line info now, right? If so, can you
> point me to a branch of llvm that can help tracing the bug down to certain
> line of code. I believe my bug is simply a write/read out of array boundary.
>
> Thanks,
> Char
>
> 在 2018-12-05 07:15:28，"Alexey Bataev" <a.bataev at hotmail.com>
> <a.bataev at hotmail.com> 写道：
>
> Hi, yes, these patches are required to have tne basic debug info support.
> At least 2 more patches are required to be able to get values of the
> variables without additional manual data type casting in cuda-gdb.
>
> Best regards,
> Alexey Bataev
>
> 4 дек. 2018 г., в 18:06, Eric Christopher <echristo at gmail.com> написал(а):
>
> Adding Alexey here who has been driving this effort in llvm.
>
> There are about 5 patches waiting on my review:
>
>    -: https://reviews.llvm.org/D54320
>    -: https://reviews.llvm.org/D46189
>    -: https://reviews.llvm.org/D51554
>    -: https://reviews.llvm.org/D46061
>    -: https://reviews.llvm.org/D45784
>
> After which I think we're good.
>
> -eric
>
> On Mon, Dec 3, 2018 at 6:29 PM Valentin Churavy via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
>> AFAIK there is work under way from IBM (couple of PRs open), but yes
>> Clang 7.0 doesn't produce the necessary information.
>>
>> -V
>>
>> On Fri, Nov 30, 2018, 14:58 treinz via llvm-dev <llvm-dev at lists.llvm.org
>> wrote:
>>
>>> Hi all,
>>> I found this
>>> http://lists.llvm.org/pipermail/llvm-dev/2017-November/118871.html when
>>> googling about compiling CUDA code using llvm. Is it still the case that
>>> one can't step into CUDA kernel code compiled by llvm in cuda-gdb? I'm
>>> using clang 7.0.
>>>
>>> Thanks,
>>> Char
>>>
>>>
>>>
>>> _______________________________________________
>>> LLVM Developers mailing list
>>> llvm-dev at lists.llvm.org
>>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>>>
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>>
>
>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20181214/905bc063/attachment.html>