search for: debuginfovariableinfo

...these to link back instructions to original C statements. I guess this is not related to the mem2reg pass. Is there a way to at least keep the stoppoint instructions? > > We're working on the required support to enable variable debug info at -O1+. > http://nondot.org/~sabre/LLVMNotes/DebugInfoVariableInfo.txt > Let us know if you'd like to contribute in this area! The llvm.dbg.value proposal looks very interesting. We would like to contribute if possible. I estimate we do not have sufficient llvm experience to contribute ourselves, but may take up a part of the work using a contractor. Can y...

...f I have to disable some specific optimizations to keep the debug > info correct that is fine. Without mem2reg pass, you're unlikely to get much optimization done on your IR. We're working on the required support to enable variable debug info at -O1+. http://nondot.org/~sabre/LLVMNotes/DebugInfoVariableInfo.txt Let us know if you'd like to contribute in this area! - Devang

...ever that is now easier to track and fix. For example, inliner is now appropriately coping info when it copies function body. This is a recent development. >> >> We're working on the required support to enable variable debug info at -O1+. >> http://nondot.org/~sabre/LLVMNotes/DebugInfoVariableInfo.txt >> Let us know if you'd like to contribute in this area! > > The llvm.dbg.value proposal looks very interesting. We would like to > contribute if possible. I estimate we do not have sufficient llvm > experience to contribute ourselves, but may take up a part of the work &g...

Hello, I use llvm and llvm-gcc as a C-to-C transformation tool using a modified version of the c backend, and rely on llvm debug instructions to link back to the original source code. Does anyone know how to get detailed line number and variable debug information at optimization levels beyond O0? Currently, I extract this debug information by compiling with -g. This works fine with

Hi All, Right now, mem2reg and SRoA strip all debug information off allocas they promote. This means that we lose almost all debug information for local variables when the optimizer is turned on. Here is a proposal to improve the situation: http://nondot.org/sabre/LLVMNotes/DebugInfoVariableInfo.txt Thoughts welcome, -Chris

Well, I am much happier now that I understand about dsymutil, and can actually step through my program in gdb. However, there are still some issues that are puzzling me. 1) First off, the debugger appears to stop at odd points. The IR for my main function looks correct to me: define i32 @"main(tart.core.Array[tart.core.String])->int"(%"tart.core.Array[tart.core.String]"*