[m-dev.] for review: a big step towards the trace-based debugger (part 1 of 3)

[Tyson Dowd]

On 26-Mar-1998, Fergus Henderson <fjh at cs.mu.OZ.AU> wrote:
> On 20-Mar-1998, Zoltan Somogyi <zs at cs.mu.OZ.AU> wrote:
> > 
> > compiler/continuation_info.m:
> > compiler/stack_layout.m:
> > 	Do not associate the stack layout information at procedure entry and
> > 	exit with the per-procedure data structure. Since we now associate this
> > 	info with the labels of those events instead, they do not need special
> > 	handling. However, do include a pointer to the call event's label's
> > 	layout structure in the per-procedure data, so that we can later
> > 	implement redo in the debugger.
> 
> When you say the "call event's label", do you mean the entry label?
> If so, please say so.
> 
> >  :- type proc_layout_info
> >  	--->	proc_layout_info(
> >  			proc_label,	% the proc label
> >  			determinism,	% which stack is used
> >  			int,		% number of stack slots
> > +			maybe(int),	% location of succip on stack
> > +			maybe(label),	% name of the label of the call event
> > +			proc_label_layout_info
> > +					% info for each internal label,
> > +					% needed for basic_stack_layouts
> >  		).
> 
> Ditto here: I don't know what "the label of the call event" means.
> 

Indeed, since the layout infos are used for multiple purposes (only one
of which is tracing), it would be best to avoid "event" as much as
possible.

-- 
       Tyson Dowd           # So I asked Sarah: what's the serial number on
                            # your computer? She replied:
     trd at cs.mu.oz.au        #          A-C-2-4-0-V-/-5-0-H-Z
http://www.cs.mu.oz.au/~trd #