search for: cudagdb

...of the sections (emit braces) •Overrides string emission (as sequence of bytes, not as strings) •Overrides emission of files/locations debug info Required changes in Clang. ================= •Add option “-gcuda-gdb” to driver. •Emit cuda-gdb compatible debug info (DWARF-2 by default + CudaGDB tuning). •Add options “-g --dont-merge-basicblocks --return-at-end” to “ptxas” call. •ptxas is able to translate debug information only if -O0 optimization level is used. It means, that we can use optimization level in LLVM > O0, but still have to use O0 when calling ptxas compiler. This a...

...s string emission (as sequence of bytes, not as strings) >>     •Overrides emission of files/locations debug info >> Required changes in Clang. >> ================= >> •Add option “-gcuda-gdb” to driver. >>     •Emit cuda-gdb compatible debug info (DWARF-2 by default + CudaGDB >> tuning). >> •Add options “-g --dont-merge-basicblocks --return-at-end” to “ptxas” >> call. >>     •ptxas is able to translate debug information only if -O0 >> optimization level is used. It means, that we can use optimization >> level in LLVM > O0, but stil...

...s string emission (as sequence of bytes, not as strings) >> •Overrides emission of files/locations debug info >> Required changes in Clang. >> ================= >> •Add option “-gcuda-gdb” to driver. >> •Emit cuda-gdb compatible debug info (DWARF-2 by default + CudaGDB >> tuning). >> •Add options “-g --dont-merge-basicblocks --return-at-end” to “ptxas” >> call. >> •ptxas is able to translate debug information only if -O0 >> optimization level is used. It means, that we can use optimization >> level in LLVM > O0, but stil...