[M3devel] cm3 regression

[Tony Hosking]

Yes, sorry, probably best to make it LONGINT.

I'll fix.

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 Apr 14, 2008, at 3:17 AM, Jay wrote:

> new source -> compiling Cstdlib.i3
> "..\src\C\32BITS\BasicCtypes.i3", line 18: illegal based LONGINT  
> literal, zero used
> "..\src\C\32BITS\BasicCtypes.i3", line 18: illegal based LONGINT  
> literal, zero used
>
>   long_long          = [-16_7fffffffffffffffL-1L ..  
> 16_7fffffffffffffffL];
>
>
> Why isn't this LONGINT? So that NT386 can limp along? And it'd be  
> correct for the rest, eh?
> I'll try it and see..
>
> The underlying system (the compiler) has (U)Int[8,16,32,64]
> They should just be used here imho..
>
> Also, what should "long" be on 64bit?
> On Windows it is 32 bits always.
> On 32 bit systems it is 32 bits.
> I think the 64bits directory is going to be forked for AMD64_NT_*.
> The Windows decision imho has successfully been applied to more code  
> and more users so therefore is better by practical success, even if  
> the whole issue is problematic almost no matter what. Clearly the C  
> and Modula-3 notions of integers are pretty poor..
>
>  - Jay
>
>
>
> > Date: Mon, 14 Apr 2008 08:52:52 +0200
> > From: wagner at elegosoft.com
> > To: m3devel at elegosoft.com
> > Subject: Re: [M3devel] cm3 regression
> >
> > Quoting Olaf Wagner <wagner at elegosoft.com>:
> >
> > > Building of libm3 now fails even in release-builds with
> > >
> > > 4539 new source -> compiling SocketPosix.m3
> > > 4540
> > > 4541 NEXT Fatal Error: bad version stamps: SocketPosix.m3
> > > 4542
> > > 4543 version stamp mismatch: Compiler.Platform
> > > 4544 <df3c2b13d1d385ee> => SocketPosix.m3
> > > 4545 <a731334c763badf8> => Compiler.i3
> > > 4546 version stamp mismatch: Compiler.ThisPlatform
> > > 4547 <92d2f58d2092154f> => SocketPosix.m3
> > > 4548 <eadfedd2877a3d59> => Compiler.i3
> > > 4549 NEXT *** execution of cm3 -build
> > > -DROOT=?/home/m3/work/cm3-ws/ 
> birch.elegosoft.com-2008-04-14-00-00-03/cm3?
> > > -DCM3_VERSION_TEXT=?d5.7.0? -DCM3_VERSION_NUMBER=?050700?
> > > -DCM3_LAST_CHANGED=?2008-03-16? && cm3 -ship
> > > -DROOT=?/home/m3/work/cm3-ws/ 
> birch.elegosoft.com-2008-04-14-00-00-03/cm3?
> > > -DCM3_VERSION_TEXT=?d5.7.0? -DCM3_VERSION_NUMBER=?050700?
> > > -DCM3_LAST_CHANGED=?2008-03-16? failed ***
> > > 4550 compile return value: 0
> > > 4551 [end compile 2008.04.14 02:54:34]
> > > 4552 *** COMPILE FAILED
> > >
> > > Does anybody understand what's going on?
> > > During upgrade(), libm3 should only be built _after_ the new  
> compiler
> > > has been installed, at least that is the intention.
> > >
> > > I'm in a hurry, so if anybody else cares to fix this, it would  
> be great.
> >
> > I sent that mail too fast. It seems that only I386_DARWIN fails in
> > the release-build, but for other reasons. The last-ok builds can
> > be expexted to fail after incompatible changes in the runtime.
> > So this should cure itself during the next days.
> >
> > We should however note that we need a full compiler bootstrap again
> > even from older d5.7.0 archives now to compile current sources.
> >
> > Olaf
> > --
> > Olaf Wagner -- elego Software Solutions GmbH
> > Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
> > phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23  
> 45 86 95
> > http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz:  
> Berlin
> > Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr:  
> DE163214194
> >
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20080414/2915ceb9/attachment-0002.html>