[m-dev.] for review: new method of handling failures, part 1 of 6

[Fergus Henderson]

On 02-Jul-1998, Zoltan Somogyi <zs at cs.mu.OZ.AU> wrote:
> 
> runtime/mercury_engine.c:
> runtime/mercury_wrapper.c:
> 	Put MR_STACK_TRACE_THIS_MODULE at the tops of these modules, so that
> 	the labels they define (e.g. do_fail and global_success) are registered
> 	in the label table when their module initialization functions are
> 	called. This is necessary for a meaningful nondet stack dump.

A quick question: this isn't going to cause mercury_trace.o to be linked in, is it?
(I don't think it will, I just want to be sure.)

> compiler/llds_out.m:
> 	Emit a #define MR_USE_REDOFR before including mercury_imp.h, to
> 	tell the runtime we are using the new failure handling scheme.
> 	This effectively changes the grade of the compiled module.

Hmm, what about the code in runtime/*.c, will that get MR_USE_REDOFR defined?
If so, how?

Apart from that, the log message looks OK.
It will take me quite a while to review the code, though...

-- 
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 128.250.37.3        |     -- the last words of T. S. Garp.