Add gprof profiling support. #7547
Conversation
|
I have updated the title description according to the recent changes. |
Rossmaxx
changed the title
|
I was wondering if it makes sense to allow gprof even in Debug mode. At least, it turned out that the results were not so far from the Release mode results. Still, I wonder if we should print a warning if gprof is active in Debug mode, so the user knows that the results may not be representative? |
|
I'll merge this in 2 days if no one objects. I choose to merge this with 1 approval because this is a trivial PR and shouldn't have any impact other than the flag |
Still, I wonder if we should print a warning if gprof is active in Debug mode, so the user knows that the results may not be representative? saw this now after I took another look. I could but I choose not to for now. I don't see any need to add a warning, building on debug mode, one should naturally know that the performance won't be good. |
This reverts commit 0256dcf.
|
I am putting a 1 week notice period for merge. Dom has a comment on including clang support, which unfortunately clang refuses to work for me the way it does for gcc. I'll put in a comment explaining the situation before merge. |
Adds gprof support for profiling the builds. Also removed the
-fomit-frame-pointerflag from swh and tap suite as the flag interferes with the-pgflag used here.per https://stackoverflow.com/questions/14666665/trying-to-understand-gcc-option-fomit-frame-pointer , this option makes getting stack traces nearly impossible, and the performance improvements seems to be negligible on 64 bit systems, especially when debugging.
to use gprof:
after building with the
WANT_DEBUG_GPROFflag turned on, run lmms, and after running,gprof ./lmms gmon.out > report.txtfrom the build directory. This will generate a text file with the profiling data. Do note that this method is tested only on GCC, and windows builds might not be supported.