[m-dev.] erlang grades

Julien Fischer juliensf at csse.unimelb.edu.au
Sat Jun 13 22:39:17 AEST 2009

On Sat, 13 Jun 2009, Julien Fischer wrote:

> On Sat, 13 Jun 2009, Peter Wang wrote:
>> On 2009-06-12, Julien Fischer <juliensf at csse.unimelb.edu.au> wrote:
>>> Hi,
>>> I'm going to add the erlang grade to the the nightly builds** on neptune
>>> (and probably goofy once it is reimaged).  The the above would be
>>> facilited if generating bytecode and native code were separate grades,
>>> i.e.
>>>    erlang    == Erlang bytecode
>>>    erlang_nc == native code
>> I suppose this is to facilitate testing only?  Otherwise I don't think
>> it's necessary.  You can mix bytecode and native code, and AFAIK if the
>> .beam file you've got is not compiled for your architecture it will fall
>> back to bytecode.  You can also (re)generate native code from a .beam file.
> Actually, if you can mix them then it's probably unnecessary.

Actually that said, there may be an issue here with how the user wants
the standard library compiled.

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

More information about the developers mailing list