search for: emitjitdebuginfofunctionrange

...ere are some minor comments, but the bigger issue of how this integrates seems important. Instead of begin a flag in TargetOptions, can this be an ExecutionEngine parameter? This doesn't look like a valid forward declaration: + raw_fd_ostream* JITEmitDebugInfoFunctionRangeStream(NULL); +EmitJitDebugInfoFunctionRange("jit-emit-debug-function-range", + cl::desc("Emit debon memory address range information, one line per function"), Typo in the cl::desc value. + // write brief debug info is requested + if (JITEmitDebugInfoFunctionRange) { + *JITEmitDebugInfoFunctionRangeStream <<...

On 06/19/2010 14:03, Yuri wrote: > This new option (--jit-emit-debug-function-range) will allow to output > function information for memory ranges that functions occupy in memory > while they run in JIT. File format generated is like this: > ... > 0x5000000 0x5001000 function_name_is_here > ... > > This feature is useful for external tools like valgrind and >