Changes between Version 10 and Version 11 of Debugging/LowLevelProfiling/Perf


Ignore:
Timestamp:
Feb 15, 2013 9:07:39 PM (2 years ago)
Author:
nfrisby
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Debugging/LowLevelProfiling/Perf

    v10 v11  
    9090which is great for pointing to the hotspots.  You can also annotate the source code (of the RTS) or the assembly, using `perf annotate`. 
    9191 
    92 == With NoFib == 
     92== Perf with !NoFib == 
    9393 
    94 There is a slight subtlety to using perf on an individual nofib test. 
     94There is a caveat to using perf on an executable built by the nofib Makefiles. 
    9595 
    9696To more accurately measure changes in binary sizes, nofib strips the symbols out of the final executable. Therefore, the useful names like "stg_ap_p_info" and "s1ql_info" will not show up in the perf report output. IE The following commands will yield information that is difficult to use. 
     
    103103}}} 
    104104 
    105 One workaround is to find the ghc options used in the log file and invoke `ghc <options from log> --make Main.hs -o test` directly. The useful symbol names will then show up in the `perf report` output. NB The symbols '''are''' in the .o files that nofib's make generates; only the linking must be done without make. 
     105One workaround is to find the ghc options used in the log file and invoke `ghc <options from log> --make Main.hs -o test` directly. The useful symbol names will then show up in the `perf report` output. NB The symbols '''are''' in the .o files that nofib's make generates; only the linking must be done without using the Makefiles.