Displaying 5 results from an estimated 5 matches for "external_symbols".
2010 Jun 19
0
[LLVMdev] [patch] New feature: debug info for function memory ranges (-jit-emit-debug-function-range)
...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 -disable-fp-elim to
generate standard prologs.
Thank you,
Yuri
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patch-debug-info.txt
URL: <http://li...
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
2010 Jun 22
2
[LLVMdev] [patch] New feature: debug info for function memory ranges (-jit-emit-debug-function-range)
...at 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 -disable-fp-elim to
> generate standard prologs.
>
> Thank you,
> Yuri
Anybody can check this in?
Yuri
2010 Jun 24
0
[LLVMdev] [patch] New feature: debug info for function memory ranges (-jit-emit-debug-function-range)
...t; ...
>> 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 -disable-fp-elim to
>> generate standard prologs.
>>
>> Thank you,
>> Yuri
>
> Anybody can check this in?
Hi Yuri,
This doesn't seem specific to the JIT...
2010 Jun 19
2
[LLVMdev] [patch] New feature: debug info for function memory ranges (-jit-emit-debug-function-range)
...ile 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 -disable-fp-elim to
> generate standard prologs.
>
> Thank you,
> Yuri
>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at...