[m-users.] Stackoverflow from --intermodule-optimisation

Paul Bone paul at bone.id.au
Wed Sep 25 13:59:56 AEST 2013

On Tue, Sep 24, 2013 at 02:08:41PM +1000, Michael Day wrote:
> Hi Paul,
>> So in this case, by performing intermodule optimisation, we've prevented the
>> standard library's compilation options form affecting the compilation of a
>> predicate whose definition comes from the standard library.
> Unfortunate. But apart from during compiler development, is there any  
> time when a user would *not* want to enable the constructor last call  
> optimisation?
> It seems that it can only ever improve the generated code, and the extra  
> time / memory usage would only be linear in the code size, so is there  
> any reason not to enable it by default?

It is reported to (comments in the manual) that it can slow programs down.
My guess is that this means the chance of slowing a program down is almost
as good as the chance that it'll speed up.

Paul Bone

More information about the users mailing list