Hello.
SH wrote 2016-02-06 16:55:
> Hello Will.
>
> You wrote 2016-02-05 14:26:52-05:00:
>> Sven wrote:
>>
>>> Is there a way to avoid the following compiler crash?
>>
>> Sorry about that.
>
> No problem. I know the status of larceny, its limitations and its
> strengths. So I can cope with
Sven Hartrumpf wrote:
> Is there a way to avoid the following compiler crash?
Sorry about that.
In my experience, this error means Larceny's assembler tried
to create a single monolithic chunk of x86 machine code whose
size was the reported 17536520 bytes, which is larger than
the maximum
16MB ought to be enough for anybody :)
The problem is likely the object layout for vectors, bytevectors,
procedures, and strings, which restricts the length field (which has a byte
count) to 24 bits. A 64-bit Larceny runtime would help. I don't think
such a runtime exists yet.
--lars
On Fri,
Hello.
Is there a way to avoid the following compiler crash?
Larceny v0.98+ "General Ripper" (Jan 26 2016 17:01:47, precise:Linux:unified)
larceny.heap, built on Di 26. Jan 17:02:56 CET 2016
>
> Compiling nall.sld
Reading larceny.scm
Reading nall-larceny.scm
WARNING from compiler:
ANF size
