[M3devel] codegen error (from Mika, new test p250)

Tony Hosking hosking at cs.purdue.edu
Sat Jan 8 22:59:33 CET 2011


I'll look into this one.

Antony Hosking | Associate Professor | Computer Science | Purdue University
305 N. University Street | West Lafayette | IN 47907 | USA
Office +1 765 494 6001 | Mobile +1 765 427 5484




On Jan 8, 2011, at 12:17 AM, Jay K wrote:

> 
> fyi, small repro:
> 
> 
> MODULE Main;
> 
> VAR x: [0L..0L];
> 
> PROCEDURE F2(<*UNUSED*>x: LONGINT) = BEGIN END F2;
> 
> BEGIN
>   F2(x);
> END Main.
> 
> (32)             start_call_direct procedure:0x4 level:0
> (33)               load var:0x2 offset:0x1A0(416) src_t:word_8 dst_t:int_32
> (34)               comment comment:********* M3CG_Check ERROR *********** bad stack:  expected [ Int64    ] got [ Int32    ]
> (35)               pop_param type:int_64
> 
> 
>  - Jay
> 
> 
> ________________________________
>> From: jay.krell at cornell.edu
>> To: m3devel at elegosoft.com; mika at async.caltech.edu
>> Subject: RE: codegen error (from Mika, new test p250)
>> Date: Thu, 6 Jan 2011 01:21:00 +0000
>> 
>> fyi:
>> 
>> jbook2:p250 jay$ rm -rf I386_DARWIN/
>> jbook2:p250 jay$ cm3 -keep
>> --- building in I386_DARWIN ---
>> 
>> new source -> compiling Main.m3
>> "../Main.m3", line 1: 1 code generation error
>> 1 error encountered
>> compilation failed => not building program "pgm"
>> Fatal Error: package build failed
>> jbook2:p250 jay$ cm3cg -y I386_DARWIN/Main.mc 2>&1 | grep -i comment
>> (4) comment comment:module global constants
>> (6) comment comment:module global data
>> (27) comment comment:F1
>> (34) comment comment:********* M3CG_Check ERROR
>> *********** bad stack: expected [ Int64 ] got [ Int32 ]
>> (43) comment comment:F2
>> (73) comment comment:Main_M3
>> (74) comment comment:module main body Main_M3
>> (83) comment comment:global constant type descriptor
>> (85) comment comment:global data type descriptor
>> (87) comment comment:module global constants
>> (90) comment comment:procedure names
>> (94) comment comment:procedure table
>> (101) comment comment:file name
>> (103) comment comment:type map for _t0174bdf4
>> (106) comment comment:type description for _t0174bdf4
>> (110) comment comment:module global data
>> (120) comment comment:typecell for _t0174bdf4
>> (141) comment comment:load map
>> (4) comment comment:module global constants
>> (6) comment comment:module global data
>> (27) comment comment:F1
>> (34) comment comment:********* M3CG_Check ERROR
>> *********** bad stack: expected [ Int64 ] got [ Int32 ]
>> (43) comment comment:F2
>> (73) comment comment:Main_M3
>> (74) comment comment:module main body Main_M3
>> (83) comment comment:global constant type descriptor
>> (85) comment comment:global data type descriptor
>> (87) comment comment:module global constants
>> (90) comment comment:procedure names
>> (94) comment comment:procedure table
>> (101) comment comment:file name
>> (103) comment comment:type map for _t0174bdf4
>> (106) comment comment:type description for _t0174bdf4
>> (110) comment comment:module global data
>> (120) comment comment:typecell for _t0174bdf4
>> (141) comment comment:load map
>> 
>> 
>> - Jay
>> 
>> 
>>> Date: Thu, 6 Jan 2011 01:26:15 +0000
>>> To: m3commit at elegosoft.com
>>> From: jkrell at elego.de
>>> Subject: [M3commit] CVS Update: cm3
>>> 
>>> CVSROOT: /usr/cvs
>>> Changes by: jkrell at birch. 11/01/06 01:26:15
>>> 
>>> Modified files:
>>> cm3/m3-sys/m3tests/src/p2/p250/: Main.m3
>>> 
>>> Log message:
>>> slightly simpler, same error
>>> 
> 		 	   		  




More information about the M3devel mailing list