Glynn Clements wrote:
>
> If you are concerned about efficiency, build GRASS with profiling
> support, and look at where the actual inefficiency lies. It would help
> to do the same for 4.x, as that is reported to be an order of
> magnitude faster than 5.x/6.x for some tasks.
Could you suggest a quick usage guide as to how to do that?
What's the best tool?
* 'gcc -pg' + gprof?
* valgrind's calltree -> kcachegrind?
(calltree doesn't need a special recompile)
How to look at the output?
Preferably compose directly to one of the wiki pages: (or make a new one)
http://grass.gdf-hannover.de/wiki/GRASS_Debugging
http://grass.gdf-hannover.de/wiki/Development
thanks,
Hamish
_______________________________________________
grass-dev mailing list
[email protected]
http://grass.itc.it/mailman/listinfo/grass-dev
