[M3devel] Compiler crash

[Tony Hosking]

I believe this is a known defect, but can you please enter a bug report into the online bug tracker?
For now, you can try expressing it in a slightly different way to get round the compiler problem (separate the IntArray as a separate variable).

On 29 Sep 2010, at 23:32, Darko wrote:

> Came across this today while compiling:
> 
> PROCEDURE NewArray(tc: INTEGER; d1, d2, d3, d4: CARDINAL := 0): Val =
>  VAR
>    d: CARDINAL;
> BEGIN
>  RETURN RTAllocator.NewTracedArray(tc, SUBARRAY(IntArray{d1, d2, d3, d4}, 0, d));
> END NewArray;
> 
> (Yes, It's not finished and won't work until d is assigned a number between 1 and 4)
> 
> ***
> *** runtime error:
> ***    <*ASSERT*> failed.
> ***    file "../src/exprs/Expr.m3", line 308
> ***
> 
> $ cm3 -version
> Critical Mass Modula-3 version 5.8.6
>  last updated: 2010-04-11
>  compiled: 2010-07-14 21:27:23
>  configuration: /Users/darko/app/cm3/bin/cm3.cfg
>  host: I386_DARWIN
>  target: I386_DARWIN
> 
> $ uname -a
> Darwin Lucifer.local 10.4.0 Darwin Kernel Version 10.4.0: Fri Apr 23 18:28:53 PDT 2010; root:xnu-1504.7.4~1/RELEASE_I386 i386
> 
> 
> I'm willing to wager it's still in the latest release.
> 
> - Darko
>