23 Oct
2006
23 Oct
'06
12:08 p.m.
Ovanes Markarian wrote:
Hello,
we have some application, where boost::shared_ptr is extensively used. After profiling with gprof I got that the shared_ptr destructor is very expensive. I used following g++ compiler flags to compile:
-Wall -ftemplate-depth-50 -fexceptions -fexpensive-optimizations -O3
It's not a good idea to use gprof to profile C++ applications. Try callgrind.
Are there may be some MACRO-defs, which can enable/disable some additional optimizations?
BTW, you did not say which platform you are on. - Volodya