I see that llvm-gcc now has some support for generating debug info when optimising - thanks! However, it still doesn't generate debug info for global variables when optimising. Is there any reason for this? With the attached patch, the whole test suite passes for me with TEST=ipodbgopt. Thanks, Jay. -------------- next part -------------- A non-text attachment was scrubbed... Name: patch.globaldebug Type: application/octet-stream Size: 609 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090529/daa5888f/attachment.obj>
Bill Wendling
2009-May-29 20:41 UTC
[LLVMdev] debug info for global variables when optimising
On Fri, May 29, 2009 at 6:24 AM, Jay Foad <jay.foad at gmail.com> wrote:> I see that llvm-gcc now has some support for generating debug info > when optimising - thanks! > > However, it still doesn't generate debug info for global variables > when optimising. Is there any reason for this? With the attached > patch, the whole test suite passes for me with TEST=ipodbgopt. >Hi Jay, The Debug Info work is still ongoing. And there are going to be still more fundamental changes in the near future. However, Devang, the person leading the effort, is on vacation now. And I don't think he's ready for this to be enabled just yet. At least, not in top of tree. -bw
Dale Johannesen
2009-Jun-01 17:48 UTC
[LLVMdev] debug info for global variables when optimising
On May 29, 2009, at 6:24 AMPDT, Jay Foad wrote:> I see that llvm-gcc now has some support for generating debug info > when optimising - thanks! > > However, it still doesn't generate debug info for global variables > when optimising. Is there any reason for this? With the attached > patch, the whole test suite passes for me with TEST=ipodbgopt.The reason is given in the comment your patch deletes. Having debug info affect the codegen is pretty bad, because you get situations where a bug goes away when you turn on debug info, and you can't debug it. TEST=ipodbgopt currently runs through -strip-debug-declare immediately, which would hide such cases. Try it with that flag removed and I bet you'll see some failures.> Thanks, > Jay.-------------- next part -------------- A non-text attachment was scrubbed... Name: patch.globaldebug Type: application/octet-stream Size: 609 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090601/1932907d/attachment.obj> -------------- next part --------------> _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
> TEST=ipodbgopt currently runs through -strip-debug-declare immediately, > which would hide such cases. Try it with that flag removed and I bet you'll > see some failures.Yes, thanks, I hadn't noticed the -strip-debug-declare. Incidentally I only "see" the failures because some "TEST-FAIL" messages whizz up and off the screen. The actual "make TEST=ipodbgopt" command completes successfully. Is that intentional? Thanks, Jay.
Possibly Parallel Threads
- [LLVMdev] debug info for global variables when optimising
- [LLVMdev] debug info for global variables when optimising
- [LLVMdev] make TEST=ipodbgopt in sqlite3: problem with TCLSH
- [LLVMdev] make TEST=ipodbgopt in sqlite3: problem with TCLSH
- [LLVMdev] Source file information.