[vsipl++] [patch] Profiler Configuration Options

[Don McCoy]

Jules Bergmann wrote:
> A better approach is to put the VSIP_IMPL_PROFILE macro in profile.hpp. 
>  That requires a bit of work because it will be defined before 
> PROFILING_ENABLED.  Something like this should work:
> 
I chose this method and added an explanatory comment in profile.hpp.

> The second comment is more of a wish that can be addressed later.  I 
> would like the ability to separately enable/disable the profiling and 
> performance APIs.  The performance API should have a lower overhead than 
> the profiling because it doesn't store data in a std::vector or 
> std::map.  Right now we can punt on this, as I'm not entire sure what 
> the performance API and profiling overheads are and how folks will 
> actually use all this.
> 
I see your point.  It shouldn't be too hard to separate the two in the 
future.  After the overhead is characterized we can decide to leave the 
performance API enabled always (if the impact is shown to be very small) 
or change it to use its own configure option.

> 
> Other than that, this looks good to check in.
> 
Committed with attached changes.  Thanks for the help.

Regards,

-- 
Don McCoy
don (at) CodeSourcery
(888) 776-0262 / (650) 331-3385, x712
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: pc2.changes
URL: <http://sourcerytools.com/pipermail/vsipl++/attachments/20060813/193d813c/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: pc2.diff
URL: <http://sourcerytools.com/pipermail/vsipl++/attachments/20060813/193d813c/attachment-0001.ksh>