wes
945ee7d93e
VTune Profiler now working with proper gcc arguments. lame.cpp now uses enough resources for VTune to capture the activity.
|
4 years ago | |
|---|---|---|
| .. | ||
| README.txt | 4 years ago | |
README.txt
07JUN20
Using -gstabs debugging tag to compile lame.exe, for VTune Profiler, we found differences in the profiling results (sometimes lame.exe/related functions would be shown
and sometimes not).
Found an Intel employee and post,
See Dennis Mochanov: https://software.intel.com/en-us/forums/vtune/topic/852219
"For MinGW binaries VTune expects debugging information in DWARF format. Make sure your application is built with -g or -gdwarf-version option"
& related post: https://software.intel.com/content/www/us/en/develop/documentation/vtune-help/top/set-up-analysis-target/linux-targets/debug-info-for-linux-binaries.html
He suggested to use the DWARF format when compiling (states that VTune expects the DWARF format for MinGW binaries), however the above link states linux targets & binaries.
We are trying to solve the issue in WINDOWS for .exe files. To see if there is an validity in using the DWARF format, we will test out his "suggested advice".
Using the above advice, using the -gdwarf-2 or -g will work with the profiler. -g is for debug info, -gdwarf is the format for the profiler.
Taking out the source path or binary/symbols path is not necessary for the setup of VTune profiler.
having the object or sources files in the working directory is not necessary.
The profiler using "pulling" at a given interval, in this case it is about 1ms. If your program executes faster than the profiler, you won't see it in the
analysis results. This is the main issue
we had for VTune aside from the gcc arguments we found mentioned above.
Using -gstabs debugging tag to compile lame.exe, for VTune Profiler, we found differences in the profiling results (sometimes lame.exe/related functions would be shown
and sometimes not).
Found an Intel employee and post,
See Dennis Mochanov: https://software.intel.com/en-us/forums/vtune/topic/852219
"For MinGW binaries VTune expects debugging information in DWARF format. Make sure your application is built with -g or -gdwarf-version option"
& related post: https://software.intel.com/content/www/us/en/develop/documentation/vtune-help/top/set-up-analysis-target/linux-targets/debug-info-for-linux-binaries.html
He suggested to use the DWARF format when compiling (states that VTune expects the DWARF format for MinGW binaries), however the above link states linux targets & binaries.
We are trying to solve the issue in WINDOWS for .exe files. To see if there is an validity in using the DWARF format, we will test out his "suggested advice".
Using the above advice, using the -gdwarf-2 or -g will work with the profiler. -g is for debug info, -gdwarf is the format for the profiler.
Taking out the source path or binary/symbols path is not necessary for the setup of VTune profiler.
having the object or sources files in the working directory is not necessary.
The profiler using "pulling" at a given interval, in this case it is about 1ms. If your program executes faster than the profiler, you won't see it in the
analysis results. This is the main issue
we had for VTune aside from the gcc arguments we found mentioned above.