[M3commit] CVS Update: cm3

[Jay K]

ok





 


Subject: Re: [M3commit] CVS Update: cm3
From: hosking at cs.purdue.edu
Date: Sat, 16 Jan 2010 19:25:29 -0500
CC: jkrell at elego.de; m3commit at elegosoft.com
To: jay.krell at cornell.edu

It would be an unnecessary complication of the compiler.  Better to leave the aborts in the library.






On 16 Jan 2010, at 14:54, Jay K wrote:

m3middle/Target.m3 knows which platforms have a stack walker.
 
 - Jay


 


From: jay.krell at cornell.edu
To: hosking at cs.purdue.edu; jkrell at elego.de
CC: m3commit at elegosoft.com
Subject: RE: [M3commit] CVS Update: cm3
Date: Sat, 16 Jan 2010 19:53:51 +0000

What I meant was, somewhere, either m3middle or m3front, or with extern pragmas, you could generate calls to abort instead of functions that call abort. Not a big deal.
 
 - Jay


 


From: hosking at cs.purdue.edu
Date: Sat, 16 Jan 2010 13:51:41 -0500
To: jkrell at elego.de
CC: m3commit at elegosoft.com
Subject: Re: [M3commit] CVS Update: cm3

m3middle?




On 16 Jan 2010, at 12:44, Jay Krell wrote:


CVSROOT: /usr/cvs
Changes by: jkrell at birch. 10/01/16 12:44:13

Modified files:
cm3/m3-libs/m3core/src/runtime/ex_frame/: RTStackC.c 

Log message:
fix warnings, optimize, calling conventions; though it seems maybe we could implement this in Modula-3 well enough?, maybe even in m3middle?


 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3commit/attachments/20100117/771f3a8a/attachment-0002.html>