> This ties in with the main question I had... typically, a > profiling layer is used on larger inputs where it is important that the > profiling code itself have very low overhead. Piggybacking on > the debug mode is a definite performance-killer, so I hope that > the profiling version of the library will be in its own inline > namespace alongside the parallel and debug modes. > > My vote for the command-line switch is -fprofile-stdlib.
I agree, on both accounts. Paolo.
