search for: emitdeclar

...ations, but when I enable optimizations, e.g. "llvm-gcc -g -O2 --emit-llvm", most of the dbg.stoppoint and dbg.declare instructions dissapear. I tried to enable at least debug.declare instructions by removing the "if(optimize) return" statement in gcc/llvm-debug.cpp, DebugInfo::EmitDeclare(), but I still do not get any dbg.declare instructions. Is there a way to keep all debug information with optimizations enabled in llvm-gcc? If I have to disable some specific optimizations to keep the debug info correct that is fine. Thanks! Martijn ------------- Martijn Rutten martijn at ma...

...imizations, e.g. "llvm-gcc -g -O2 > --emit-llvm", > most of the dbg.stoppoint and dbg.declare instructions dissapear. > > I tried to enable at least debug.declare instructions by removing the > "if(optimize) return" statement in gcc/llvm-debug.cpp, > DebugInfo::EmitDeclare(), but I still do not get any dbg.declare > instructions. This will enable dbg.declare, but they'll be removed by mem2reg pass immediately. > Is there a way to keep all debug information with optimizations > enabled in llvm-gcc? > If I have to disable some specific optimizations...

...lvm-gcc -g -O2 >> --emit-llvm", >> most of the dbg.stoppoint and dbg.declare instructions dissapear. >> >> I tried to enable at least debug.declare instructions by removing the >> "if(optimize) return" statement in gcc/llvm-debug.cpp, >> DebugInfo::EmitDeclare(), but I still do not get any dbg.declare >> instructions. > > This will enable dbg.declare, but they'll be removed by mem2reg pass > immediately. > >> Is there a way to keep all debug information with optimizations >> enabled in llvm-gcc? >> If I have to di...

...even then it could be improved. For example, picking on the frontend for a bit, we spend 10% of "-emit- llvm -O0 -g -c" time in DebugInfo::EmitFunctionStart, most of which is spent recursively walking the debug info with DISerializer. We also spend 9.3% of the time in DebugInfo::EmitDeclare, 10% of the time in eraseLocalLLVMValues, 12% of the time writing the .bc file (which isn't relevant to normal use), 21% of time parsing (which we can't help), Anyone interested in picking off a piece and tackling it? -Chris -------------- next part -------------- An HTML attachm...

Hi Duncan, I came across something like the following recently which I guess might be related to your recent work. Any ideas? $ clang++-tot -cc1 crash_on_invalid.cpp -g -emit-obj -fexceptions -fcxx-exceptions crash_on_invalid.cpp:13:1: error: C++ requires a type specifier for all declarations x; ^ 1 error generated. *** Error in `clang++-tot': corrupted double-linked list: 0x000000000754f340

...s/dexonsmith/data/llvm.asan/staging/bin/clang+0x10158ac1a) > #3 0x10c3af5ed in llvm::DebugLoc::get(unsigned int, unsigned int, > llvm::MDNode*, llvm::MDNode*) > (/Users/dexonsmith/data/llvm.asan/staging/bin/clang+0x10148e5ed) > #4 0x10d4fa18c in > clang::CodeGen::CGDebugInfo::EmitDeclare(clang::VarDecl const*, > llvm::dwarf::LLVMConstants, llvm::Value*, unsigned int, > llvm::IRBuilder<true, llvm::ConstantFolder, > clang::CodeGen::CGBuilderInserter<true> >&) > (/Users/dexonsmith/data/llvm.asan/staging/bin/clang+0x1025d918c) > #5 0x10d517b0d in &gt...