[m-dev.] question about mode representation

Peter Wang novalazy at gmail.com
Sun Apr 1 11:11:38 AEST 2018

On Fri, 30 Mar 2018 17:02:31 +1100 (AEDT), "Zoltan Somogyi" <zoltan.somogyi at runbox.com> wrote:
> A constraint based mode analysis algorithm would make decisions about
> "does this goal produce X, or consume it?" directly, so translating
> its decisions back into the form of instmap_deltas would be a giant step
> backwards. We need a new type to record, in each goal's goal_info,
> information such as
> - which variables (or parts of variables) did this goal produce?
> - which variables (or parts of variables) had the range of their possible
>   values reduced (e.g. from "f or g or h" to just "f or h")?
> Like instmap_deltas, it will have a way to record that the program point
> after the goal is unreachable. It will also need to have ways to record
> which variables become non-unique (when their alias is taken), with a later
> extension to record which variables become unique again (when their last alias
> goes out of scope).
> I have two questions for everyone.
> The first is: what should this new goal_info field, and its type, be called?

var_modes? var_inst_deltas?

goal_mode(s) sounds acceptable.


More information about the developers mailing list