search for: treinz

...his! 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 o...

Hi Char, I found the problem, for some reason the last patch was applied correctly. Just committed the fixed version. Tried to compile axpy.cu, everything works. ------------- Best regards, Alexey Bataev 23.01.2019 13:37, treinz пишет: > Hi Alexey, > > I tried the b7195a6 from the llvm github mirror, which does include > your commit D46189 <https://reviews.llvm.org/D46189> (see below). But > it can't compile the example program > on https://llvm.org/docs/CompileCudaWithLLVM.html#invoking-clang &...

...work around the aforementioned ptxas bug. Thanks, Char At 2019-02-28 02:09:54, "Alexey Bataev" <a.bataev at outlook.com> wrote: Hi Char, it looks like they have some kind of buffer overflow bug in their ptxas tool. ------------- Best regards, Alexey Bataev 27.02.2019 13:08, treinz пишет: Hi Alexey, I submitted the bug report to nvidia. While they are working on it, can you share some insight in what could potentially cause this? I just want to get a sense if such a bug require significant amount of work to fix, which can help me make some decision moving forward with my p...

...r do I need to wait for llvm 10 releaase. Thanks, Char At 2019-02-28 02:09:54, "Alexey Bataev" <a.bataev at outlook.com> wrote: Hi Char, it looks like they have some kind of buffer overflow bug in their ptxas tool. ------------- Best regards, Alexey Bataev 27.02.2019 13:08, treinz пишет: Hi Alexey, I submitted the bug report to nvidia. While they are working on it, can you share some insight in what could potentially cause this? I just want to get a sense if such a bug require significant amount of work to fix, which can help me make some decision moving forward with my p...

...; wrote: Hi Char, yes, this line causes the crash. You don't need .cu files (I don't know what files are you talking about, clang does not generate .cu files). You need just this .s file to reproduce the error and nothing else. ------------- Best regards, Alexey Bataev 26.02.2019 13:06, treinz пишет: Hi Alexey, Just want to make sure I understand what you said because I'm not familiar with the llvm pipeline, it's this line: /net/gs/vol3/software/modules-sw/cuda/10.0/Linux/RHEL6/x86_64/bin/ptxas" -m64 -g --dont-merge-basicblocks --return-at-end -v --gpu-name sm_75 --outp...

...ed to report the bug to NVidia, but you need to manually run the ptxas tool with the generated .s file. Sometimes it helps to compile the code sequentially, not using the parallel builds. Plus, those crashes may disappear from time to time. Best regards, Alexey Bataev 25 февр. 2019 г., в 19:59, treinz <treinz at 163.com> написал(а): Hi Alexey, Thanks for the great work! The version I checked out works most of the time. But I do encounter crashes sometimes. I can't file a bug report on https://bugs.llvm.org/ because I don't have an account. I sent an email to bugs-admin at lists...

...63f86fe50b9a101 from github mirror. The bug is reproducible on my machine with a nvidia RTX2080 card (sm=Turing75). Thanks, Char At 2019-01-24 03:25:39, "Alexey Bataev" <a.bataev at outlook.com> wrote: Yes, this one. ------------- Best regards, Alexey Bataev 23.01.2019 14:17, treinz via llvm-dev пишет: Hi Alexey, Thanks for working on this. I assume the last commit you mentioned is: commit 48aefa8877713616802d9c90b63f86fe50b9a101 (HEAD -> master, origin/master, origin/HEAD) Author: Alexey Bataev <a.bataev at hotmail.com> Date: Wed Jan 23 18:59:54 2019 +0000...

...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 us...

...-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 CUD...

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 -------------- next part -------------- An HTML attachment was scrubbed... URL: