[m-dev.] Thoughts on binary back-ends

Thomas Conway conway at cs.mu.OZ.AU
Fri Jun 22 10:03:25 AEST 2001

On Thu, Jun 21, 2001 at 08:35:17PM EST, Ralph Becket wrote:
> > From: Fergus Henderson [mailto:fjh at cs.mu.OZ.AU]
> > Sent: 21 June 2001 02:58
> > 
> > On 19-Jun-2001, Ralph Becket <rbeck at microsoft.com> wrote:
> > > I've been thinking about compiler back-ends and been looking at
> > > C-- and MLRISC and so forth (I admit it's not something I've
> > > studied extensively).  These are some preliminary thoughts on
> > > the subject - I'd be interested to hear other people's views
> > > and opinions.
> > 
> > What problem are you trying to solve?
> * Compilation time.
> * Access to/control over stack frame format (e.g. it might be 
> interesting to examine cactus stacks for concurrency).

FWIW, I have a patch somewhere that implements heap allocated stack
frames (buggy for the nondet stack still) and suspension analysis.
For computations that cannot suspend we can use the normal stacks,
and for computations that may suspend we can use heap allocated stack
frames. This drastically reduces the size of an MR_Context (which in
my thesis I'm calling MR_Task since task is a less confusing term -
one day I might even write the necessary sed/perl script), and makes
highly concurrent programs much more feasible.

  Thomas Conway )O+
 <conway at cs.mu.oz.au>       499 User error! Replace user, and press any key.
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