I tried again, and did "make compiler". Even with 5.5.1 Development, and maxInlineSize:=1, MLton is just too big for polyml:
Exception- InternalError: fixupConstantLoad: constant too distant (16-bit offset) raised while compiling Adam On Fri, Apr 26, 2013 at 5:14 PM, Adam Goode <[email protected]> wrote: > Oh no, I messed that up. I will try again. Thanks for noticing. > > On Apr 26, 2013 3:43 PM, "David Matthews" <[email protected]> > wrote: >> >> Just to be absolutely clear: you did run "make compiler" after running >> "make", didn't you? You should get >> Poly/ML 5.5.1 Development >> before the prompt. >> >> David >> >> On 26/04/2013 20:29, Adam Goode wrote: >>> >>> I built from svn trunk last night, and still had the same problem. So, >>> no luck. Thanks for trying! >>> >>> >>> Adam >>> >>> >>> On Thu, Apr 25, 2013 at 7:49 AM, David Matthews >>> <[email protected]> wrote: >>>> >>>> On 24/04/2013 15:20, Adam Goode wrote: >>>>> >>>>> >>>>> Bad news, I tried PolyML.Compiler.maxInlineSize := 1 and it still >>>>> fails. >>>>> >>>>> Any other ideas? If I were to work on 32-bit jumps, are there binary >>>>> compatibility issues you can think of? >>>> >>>> >>>> >>>> I think there could be problems because the offset used in the >>>> instruction >>>> that loads a value from the constant area at the end of the code is also >>>> 16-bit. That limits the distance from that instruction to the end of >>>> the >>>> code. However, it looks as though the jump instructions use signed >>>> 16-bit >>>> offsets where the other cases use unsigned. I've committed a change >>>> that >>>> uses unsigned 16-bit offsets for jumps and splits the 16-bit jumps into >>>> forward and backwards cases. Could you try this and see if it works? >>>> You >>>> will need to build the compiler (make compiler) to pick up the change. >>>> If >>>> not you're welcome to see if you can come up with a fix. >>>> >>>> David _______________________________________________ polyml mailing list [email protected] http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
