search for: jitemitdebuginfofunctionrangestream

...erator, and have the JIT leverage off that? Here 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) { + *JITEm...

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 >

...how this integrates seems important. > Why this isn't specific to JIT? It outputs memory addresses of functions while they are run in JIT. Can code be run within LLVM in some other way than JIT? > This doesn't look like a valid forward declaration: > > + raw_fd_ostream* JITEmitDebugInfoFunctionRangeStream(NULL); > This isn't the forward declaration, but the definition of the static value. Yuri

...y are run in JIT. Can code be run within LLVM in some other way than JIT? I don't know, good question. If it really is specific to the JIT, please sink it down into JIT specific code. > >> This doesn't look like a valid forward declaration: >> >> + raw_fd_ostream* JITEmitDebugInfoFunctionRangeStream(NULL); >> > > This isn't the forward declaration, but the definition of the static value. Ok, well that is extremely non-obvious. Please use initialization syntax with "= NULL". -Chris