search for: d40778

+ 1 to having this functionality implemented as `llvm-as -g` or some analog (`clang -g foo.ll`). As I outlined in https://reviews.llvm.org/D40778 <https://reviews.llvm.org/D40778>, I think such a solution can be made to work for JIT users who don't have on-disk *.ll files. > On Mar 21, 2018, at 5:37 PM, Jason Surprise via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > We have implemented a debug pass to enable de...

...there's the question of whether we should preserve >> existing debug information in an LLVM IR file or write over it when it >> is given to Clang. >> >> Any thoughts on this? >> >> [1] https://reviews.llvm.org/rL222945 >> [2] https://reviews.llvm.org/D40778 >> [3] https://bugs.llvm.org/show_bug.cgi?id=35770 >> >> Thanks, >> Dan. >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >...

...info to the Llvm module about LLVM IR, at which point one can throw the executable into any debugger and get llvm level debugging. I've started a patch to revive this feature (DebugIR pass). I've been sidetracked the past month, but I'll come back to it soon :) https://reviews.llvm.org/D40778 Cheers, Siddharth On Thu 4 Jan, 2018, 09:23 Brenda So via llvm-dev, <llvm-dev at lists.llvm.org> wrote: > Hi > > I am looking at open projects that LLVM want to implement and it seems to > be a suggestion to write an LLVM IR level debugger. Is there any existing > LLVM proje...

...ed to fix [3]. Although this probably needs more though because there's the question of whether we should preserve existing debug information in an LLVM IR file or write over it when it is given to Clang. Any thoughts on this? [1] https://reviews.llvm.org/rL222945 [2] https://reviews.llvm.org/D40778 [3] https://bugs.llvm.org/show_bug.cgi?id=35770 Thanks, Dan.

Hi I am looking at open projects that LLVM want to implement and it seems to be a suggestion to write an LLVM IR level debugger. Is there any existing LLVM projects out there that already does such a thing? If not, I would like to try implementing one myself. By debugger, I think it means something like gdb, where you can insert breakpoints, run code and observe layout of registers and memory at

...needs > more though because there's the question of whether we should preserve > existing debug information in an LLVM IR file or write over it when it > is given to Clang. > > Any thoughts on this? > > [1] https://reviews.llvm.org/rL222945 > [2] https://reviews.llvm.org/D40778 > [3] https://bugs.llvm.org/show_bug.cgi?id=35770 > > Thanks, > Dan. > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > -- Sent from my iPhone ---------...

...about LLVM IR, at which point > one can throw the executable into any debugger and get llvm level debugging. > > I've started a patch to revive this feature (DebugIR pass). I've been > sidetracked the past month, but I'll come back to it soon :) > https://reviews.llvm.org/D40778 > > Cheers, > Siddharth > > On Thu 4 Jan, 2018, 09:23 Brenda So via llvm-dev, <llvm-dev at lists.llvm.org> > wrote: > >> Hi >> >> I am looking at open projects that LLVM want to implement and it seems to >> be a suggestion to write an LLVM IR level...