[m-dev.] For review: print trail information in report_stats/0

Fergus Henderson fjh at cs.mu.OZ.AU
Wed May 26 13:00:24 AEST 1999

On 25-May-1999, Warwick Harvey <wharvey at cs.monash.edu.au> wrote:
> I'm not sure about this whole ``list thing'' for dumping the statistics out 
> in report_stats/0.  I suppose it was historical, but particularly if memory 
> profiling is being done, it seems a bit silly now.

I've found the brackets useful as a way of distinguishing between a program's
normal output and the additional profiling output that results from inserting
calls to report_stats.

> Anyway, I've tried to 
> maintain reasonable formatting for different grade option combinations, 
> though the no trail and no garbage collection combination might look a 
> little odd (the heap usage would be printed on its own at the start of a 
> line when it would have fit on the end of the previous one).  This can be 
> fixed at the expense of complicating the code, but I doubt it's worth it.

I agree, this is not worth worrying about for now.

> library/benchmarking.m:
> 	Added the printing of information about the trail to
> 	ML_report_stats() (and hence report_stats/0).
> 	Also fixed some cosmetic errors (e.g. if the conservative garbage
> 	collector was not used, the list was terminated twice).

That change looks fine.  Thanks.

Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh>  |  of excellence is a lethal habit"
PGP: finger fjh at        |     -- the last words of T. S. Garp.
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au

More information about the developers mailing list