[m-rev.] ssdb v1.0 fixed

Ian MacLarty maclarty at csse.unimelb.edu.au
Wed Dec 12 12:00:14 AEDT 2007


On Tue, Dec 11, 2007 at 07:01:17PM +1100, Zoltan Somogyi wrote:
> On 06-Dec-2007, Ian MacLarty <maclarty at csse.unimelb.edu.au> wrote:
> > optimisations that occur later.  If you do it later, then you
> > have to turn off all optimisations.
> > 
> > As I understand it, the transformed code is still valid Mercury, so
> > there should at least be some optimisations that will work on it.
> 
> That depends on what you mean by "work". Most optimizations won't introduce
> any bugs for the code generated by the ssdb transformation (so they "work"
> in one sense), but as soon as they see the impurity annotations, most
> optimizations will leave the code alone, which means they won't improve
> the code at all (so they do *not* "work" in another sense).
> 

Yes, *most* will leave the code alone, but maybe *some* (current or
future) will make it faster.

Ian.
--------------------------------------------------------------------------
mercury-reviews mailing list
Post messages to:       mercury-reviews at csse.unimelb.edu.au
Administrative Queries: owner-mercury-reviews at csse.unimelb.edu.au
Subscriptions:          mercury-reviews-request at csse.unimelb.edu.au
--------------------------------------------------------------------------



More information about the reviews mailing list