search for: rl222945

...necessary. This work could also be used 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.

...his 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. >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org >> http://lists.llv...

...t >> is given to Clang. If foo.ll contains edited debug info, `clang -g` shouldn't silently drop the edits. A warning + no-op seems more appropriate. Happy to help with code review! thanks, vedant >> >> Any thoughts on this? >> >> [1] https://reviews.llvm.org/rL222945 <https://reviews.llvm.org/rL222945> >> [2] https://reviews.llvm.org/D40778 <https://reviews.llvm.org/D40778> >> [3] https://bugs.llvm.org/show_bug.cgi?id=35770 <https://bugs.llvm.org/show_bug.cgi?id=35770> >> >> Thanks, >> Dan. >> _____________...

...be used 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. > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-d...