c++ - using gprof and boost -
while profiling bit of code use's many boost functions gprof, there nasty , hard follow output see sample below , there way clean gprof use boost or more boost friendly alternatives? looks of there repition of boost::math::policy cluttering profiling output making difficult see or understand call graph
btw heres snippet of example
boost::math::policies::policy<boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy> >(long double, long double, long double*, long double*, int, boost::math::policies::policy<boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy> const&)
i think prefer callgrind gprof. it's part of valgrind, have it. can use kcachegrind view results graphically.
Comments
Post a Comment