[mercury-users] Generating small and fast binaries in Mercury

Julien Fischer juliensf at csse.unimelb.edu.au
Fri Jul 6 14:18:47 AEST 2007

On Thu, 5 Jul 2007, Jonathan Morgan wrote:

> On 7/3/07, Ralph Becket <rafe at csse.unimelb.edu.au> wrote:
>> Jonathan Morgan, Monday,  2 July 2007:
>> >
>> > There is a tool that tries to get the best results (faster code,
>> > smaller executables, or whatever your criteria is) for any Mercury
>> > program, called gator.  You will find it in mercury-extras, with
>> > instructions on how to use it.  I imagine that it would take quite a
>> > while working with the mercury compiler, given how large a code base
>> > it is.
>> When we ran tests with gator we found that -O5 produced much the best 
>> results.
>> Different programs may benefit from different tweaks for the other 
>> settings.
> What optimisation settings are used for the source distributions (e.g.
> what the ordinary user is likely to be using)?

The default optimization settings don't depend on how the compiler
was built.  The C code for the source distribution is built with
-O2 --intermodule-optimization --cross-compiling, but that is more
of a resource issue - if jupiter was a faster machine we'd build
it at -O5 (as we used to).


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

More information about the users mailing list