<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Sorry, no.<BR>
Point there was considering forcing records into memory to help pass them<BR>
as parameters but I abandoned that approach anyway.<BR>
It caused other problems -- specifically an assertion failure in the backend<BR>
related to records and nested functions. Current source passes on more type information<BR>
than ever before to compiler, and is working in some ways more than<BR>
ever before, but there are problems under optimization that need more investigation.<BR>
<BR>
<BR>
We only pass on an "intermediate" level of type information, and the frontend<BR>
does layout itself, so while "good", it is also dangerous. Anyway, to be looked<BR>
into further.<BR>
<BR>
<BR>
The unfortunate plain truth, it seems, is we have a fairly large code base,<BR>
with little use, and little expertise. The original authors are all gone.<BR>
<BR>
<BR>
I don't know cvsup.<BR>
Given how poor cvs is in the first place, and how many promising alternatives there are now,<BR>
it seems a waste to invest in learning to use cvsup, or spending much time debugging it and fixing it.<BR>
But maybe we'll get it working.<BR>
<BR>
<BR>
- Jay<BR><BR> <BR>
> Date: Mon, 6 Sep 2010 22:36:26 +0000<BR>> From: dabenavidesd@yahoo.es<BR>> To: m3devel@elegosoft.com; hendrik@topoi.pooq.com<BR>> Subject: Re: [M3devel] cvsup crash<BR>> <BR>> Hi all:<BR>> perhaps this change was made in support of that days before:<BR>> https://mail.elegosoft.com/pipermail/m3commit/2010-September/008793.html<BR>> need to check it really what that means.<BR>> This perhaps relates to the abstract visibility of memory of the M3CG machine?<BR>> A similar setting could be written on the ldb debugger as it mentioned the Cedar Abstract machine setting as an example for using its Abstract Memory Interfaces, on which could had interactive debuggers interpreters.<BR>> This all was based on the Mesa stack machine with some basic extension for Automatic Storage Management. There some types of docs related to it on:<BR>> http://www.digibarn.com/friends/alanfreier/princops/00yTableOfContents.html<BR>> Hope this helps a bit<BR>> <BR>> --- El lun, 6/9/10, hendrik@topoi.pooq.com <hendrik@topoi.pooq.com> escribió:<BR>> <BR>> > De: hendrik@topoi.pooq.com <hendrik@topoi.pooq.com><BR>> > Asunto: [M3devel] cvsup crash<BR>> > Para: m3devel@elegosoft.com<BR>> > Fecha: lunes, 6 de septiembre, 2010 14:50<BR>> > Is this a known problem? From<BR>> > the mentions of cvsup on this list a few <BR>> > months ago I suspect it might be. But I'm mentioning<BR>> > it in case it's <BR>> > not known.<BR>> > <BR>> > I installed cm3 from the cm3-LINUXLIBC6-REL.deb I<BR>> > downloaded on Sept 5.<BR>> > I than ran cvsup to update my copy of the Modula 3 CVS that<BR>> > I acquired <BR>> > some months ago. This time I did specify the<BR>> > 'cvsroot' option I had <BR>> > forgotten that time.<BR>> > <BR>> > But this time, cvsup crashed:<BR>> > <BR>> > hendrik@lovesong:~/newcm3/trywholecvs$ cvsup cvsupfile-cm3<BR>> > <BR>> > <BR>> > ***<BR>> > *** runtime error:<BR>> > *** An array subscript was out of range.<BR>> > *** file "../src/vbt/VBTRep.m3", line 644<BR>> > ***<BR>> > <BR>> > Aborted<BR>> > hendrik@lovesong:~/newcm3/trywholecvs$ <BR>> > <BR>> > <BR>> > Just in case it's relevant, my cvsupfile-cm3 file:<BR>> > <BR>> > #<BR>> > # If not running X, or invoking cvsup from a<BR>> > non-interactive script, <BR>> > then<BR>> > # run it as follows:<BR>> > #<BR>> > # cvsup -g -L 2 cvsupfile.cm3<BR>> > #<BR>> > # To use the GUI, omit the -g option<BR>> > #<BR>> > <BR>> > # Defaults that apply to all the collections<BR>> > <BR>> > # This host address is permanent:<BR>> > *default host=modula3.elegosoft.com<BR>> > <BR>> > # Please change the local destination as you like<BR>> > # *default base=/usr/tmp/cvs<BR>> > # *default prefix=/usr/tmp/cvs<BR>> > *default base=/farhome/hendrik/newcm3/trywholecvs/cvs<BR>> > *default prefix=/farhome/hendrik/newcm3/trywholecvs/cvs<BR>> > <BR>> > # Use release=cvs to get the full repository, . to checkout<BR>> > the latest<BR>> > # sources, or a cvs tag<BR>> > *default release=cvs<BR>> > *default delete use-rel-suffix<BR>> > <BR>> > # If your network link is a T1 or faster, comment out the<BR>> > following <BR>> > line.<BR>> > *default compress<BR>> > *default preserve<BR>> > <BR>> > # cm3 is the complete source file collection, including<BR>> > everything<BR>> > # I had access to from the CM3 4.1 and CM3 5.1 releases<BR>> > made by Critical<BR>> > # Mass, Inc., and all subsequent updates, fixes, and<BR>> > additions of the<BR>> > # open source CM3 distribution<BR>> > # cm3 includes all the cm3-xxx collections below<BR>> > cm3<BR>> > <BR>> > # scanner and parser generators from the California<BR>> > Institute of <BR>> > Technology<BR>> > #cm3-caltech-parser<BR>> > <BR>> > # cm3 documentation in html and pdf format<BR>> > #cm3-doc<BR>> > <BR>> > # cm3 communication packages distribution (tcp, network<BR>> > objects, serial <BR>> > lines)<BR>> > #cm3-m3-comm<BR>> > <BR>> > # cm3 database related packages (odbc, smalldb, stablegen,<BR>> > postgres)<BR>> > #cm3-m3-db<BR>> > <BR>> > # miscellaneous cm3 demo programs (cube, calculator,<BR>> > fisheye, <BR>> > sharedboard,<BR>> > # mentor)<BR>> > #cm3-m3-demo<BR>> > <BR>> > # games (columns, badbricks, tetris, solitaire, maze)<BR>> > #cm3-m3-games<BR>> > <BR>> > # the lectern documentation tools packages<BR>> > #cm3-m3-lectern<BR>> > <BR>> > # cm3 standard libraries (m3core, libm3, lists, tables,<BR>> > tempfiles, <BR>> > digraphs, <BR>> > # slisp, parseparams, realgeometry, libsio)<BR>> > #cm3-m3-libs<BR>> > <BR>> > # mail packages (llscan, postcard, webcard)<BR>> > #cm3-m3-mail<BR>> > <BR>> > # packages related to the obliq language<BR>> > #cm3-m3-obliq<BR>> > <BR>> > # the SRC package tools<BR>> > #cm3-m3-pkgtools<BR>> > <BR>> > # m3 and quake comopiler, linker, interpreter, installation<BR>> > and support<BR>> > #cm3-m3-sys<BR>> > <BR>> > # miscellaneous tools from pretty printing to heap and<BR>> > thread monitors<BR>> > #cm3-m3-tools<BR>> > # graphical user interface packages (trestle, X11, motif,<BR>> > formsvbt,<BR>> > # videovbt, zeus etc.)<BR>> > #cm3-m3-ui<BR>> > <BR>> > # WWW related packages (http, proxy, web, webcat, webscape,<BR>> > deckscape)<BR>> > #cm3-m3-www<BR>> > <BR>> > # cm3 shell scripts<BR>> > #cm3-scripts<BR>> > <BR>> > # cm3 WWW pages<BR>> > #cm3-www<BR>> > <BR>> > # a CVSROOT directory<BR>> > cvsroot<BR>> > <BR>> > <BR>> > The cvsup I used identifies itself as:<BR>> > <BR>> > hendrik@lovesong:~$ cvsup -v<BR>> > CVSup client, GUI version<BR>> > Copyright 1996-2003 John D. Polstra<BR>> > Software version: release_branch_cm3_5_8<BR>> > Protocol version: 17.0<BR>> > Operating system: LINUXLIBC6<BR>> > http://www.cvsup.org/<BR>> > Report problems to cvsup-bugs@polstra.com<BR>> > CVSup is a registered trademark of John D. Polstra<BR>> > hendrik@lovesong:~$ <BR>> > <BR>> > <BR>> > -- hendrik<BR>> > <BR>> > <BR>> <BR>> <BR>> <BR> </body>
</html>