Displaying 4 results from an estimated 4 matches for "gprof2dot".
2013 Jul 14
5
[LLVMdev] Analysis of polly-detect overhead in oggenc
...are called.
>
>Did you try running 'perf record' with the '-g' option? This should give
>you callgraph information, that should be very helpful to track down the
>callers in Polly. Also, if you prefer a graphical view of the
>results, you may want to have a look at Gprof2Dot [1]. Finally, if this
>all does not work, just running Polly in gdb and randomly breaking a
>couple of times (manual sampling), may possibly hint you to the right place.
>
I also tried perf with -g, but it report nothing useful. the result of perf -g is:
- 48.70% opt opt...
2013 Jul 14
0
[LLVMdev] Analysis of polly-detect overhead in oggenc
...gt;
>>Did you try running 'perf record' with the '-g' option? This should give
>>you callgraph information, that should be very helpful to track down the
>>callers in Polly. Also, if you prefer a graphical view of the
>>results, you may want to have a look at Gprof2Dot [1]. Finally, if this
>>all does not work, just running Polly in gdb and randomly breaking a
>>couple of times (manual sampling), may possibly hint you to the right
>> place.
>>
>
> I also tried perf with -g, but it report nothing useful. the result of perf
> -g is:...
2013 Jul 14
0
[LLVMdev] Analysis of polly-detect overhead in oggenc
...are called.
>
>Did you try running 'perf record' with the '-g' option? This should give
>you callgraph information, that should be very helpful to track down the
>callers in Polly. Also, if you prefer a graphical view of the
>results, you may want to have a look at Gprof2Dot [1]. Finally, if this
>all does not work, just running Polly in gdb and randomly breaking a
>couple of times (manual sampling), may possibly hint you to the right place.
>
I also tried perf with -g, but it report nothing useful. the result of perf -g is:
- 48.70% opt opt...
2013 Jul 14
2
[LLVMdev] Analysis of polly-detect overhead in oggenc
...Did you try running 'perf record' with the '-g' option? This should give
>>>you callgraph information, that should be very helpful to track down the
>>>callers in Polly. Also, if you prefer a graphical view of the
>>>results, you may want to have a look at Gprof2Dot [1]. Finally, if this
>>>all does not work, just running Polly in gdb and randomly breaking a
>>>couple of times (manual sampling), may possibly hint you to the right
>>> place.
>>>
>>
>> I also tried perf with -g, but it report nothing useful. the re...