Displaying 5 results from an estimated 5 matches for "function_name_is_here".
2010 Jun 16
6
[LLVMdev] [patch] New feature: debug info in add2line format (--jit-emit-debug-addr2line)
This new option will allow to output function information in the same
format as addr2line from binutils emits:
...
0xABCDEF01 T function_name_is_here
...
This feature is useful to profile the code when it is run in JIT by
external tools like valgrind and google-perftools.
For example, google-perftools runs addr2line on executable and uses the
resulting file to resolve memory addresses to function names. In case of
LLVM JIT the resulting from...
2010 Jun 19
0
[LLVMdev] [patch] New feature: debug info for function memory ranges (-jit-emit-debug-function-range)
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
google-perftools to profile the code when it is run in JIT. Particularly
google-perftools will have a special option (--external_symbols) that
will be able to import this file.
Note: to be useful this flag should be used with -dis...
2010 Jun 22
2
[LLVMdev] [patch] New feature: debug info for function memory ranges (-jit-emit-debug-function-range)
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
> google-perftools to profile the code when it is run in JIT.
> Particularly google-perftools will have a special option
> (--external_symbols) that will be able to import this file.
>
> Note: to be use...
2010 Jun 24
0
[LLVMdev] [patch] New feature: debug info for function memory ranges (-jit-emit-debug-function-range)
.../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
>> google-perftools to profile the code when it is run in JIT.
>> Particularly google-perftools will have a special option
>> (--external_symbols) that will be able to import this file....
2010 Jun 19
2
[LLVMdev] [patch] New feature: debug info for function memory ranges (-jit-emit-debug-function-range)
...at 2:03 PM, Yuri <yuri at rawbw.com> 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 google-perftools
> to profile the code when it is run in JIT. Particularly google-perftools
> will have a special option (--external_symbols) that will be able to import
> this file.
>
> Note: to be useful...