[M3devel] Fwd: Returned mail: see transcript for details

[Tony Hosking]

Ah, yes the Windows (non-gcc) x86 backed will certainly need fixing  
to handle 64-bit integers.  I had forgotten that Windows does not use  
the gcc-based backend.  The principal differences can probably be  
figured out by looking at how Long.m3 gets compiled.  Take a look at  
the changes to M3CG_Ops.i3 to get a sense for what changes were made  
to the interface between the middle and back ends.

On Aug 11, 2007, at 2:53 PM, j k wrote:

> Ok, other than calling it "the x86 backend", I think I'm right. I  
> wasn't sure if it was for all x86 platforms or just Windows.
>
> How about the "non gcc" backend? I think only Windows uses it and  
> no other platform.
>
> I can get much further still having fixed BuildStandalone  
> functionality in m3-sys\cminstall\src\config\NT386. I broke it a  
> few months ago. I got as far as m3ui and something with RTHeapDep,  
> I think the problem there is the interface got deleted between the  
> last binary distribution and now. I'll dig a bit more.
>
> After fixing BuildStandalone, tried again with the inline Long.m3  
> and got the same errors so I put back my  C implementation -- I am  
> NOT sure it is right, either in calling convention or in  
> implementing the shift/rotate/extract/insert stuff correctly.
>
> Now cm3 -ship works on m3core.dll as well but that's a different  
> point.
>
>  - Jay
>
> From: jayk123 at hotmail.com
> To: hosking at cs.purdue.edu; m3devel at elegosoft.com
> Date: Sat, 11 Aug 2007 17:55:06 +0000
> Subject: Re: [M3devel] Fwd: Returned mail: see transcript for details
>
> Yeah sorry I have to fix that forwarding, been broken for months  
> but almost have it fixed.
> jayk123 at hotmail.com works.
>
> Hm. Geez I don't know. I guess I should stop submitting for now.  
> Let me figure more stuff out.
>
> I built cm3.exe and am running it. I had more errors before fixing  
> the Windows clearenv.cmd, I submitted a fix for it -- it was  
> clearing %cm3%.
>
> I have to track down where the gcc vs. no gcc decision is made.  
> Maybe it is only x86 Windows that uses this code, not all x86  
> platforms?
>
> I can get further with my changes but then I crash and I probably  
> won't make much more progress today.
>
>  - Jay
>
> > From: hosking at cs.purdue.edu
> > Date: Sat, 11 Aug 2007 13:19:56 -0400
> > To: m3devel at elegosoft.com
> > Subject: [M3devel] Fwd: Returned mail: see transcript for details
> >
> > Jay, your e-mails are bouncing.
> >
> > Begin forwarded message:
> >
> > > From: Mail Delivery Subsystem <MAILER-DAEMON at cornell.edu>
> > > Date: August 11, 2007 1:15:10 PM EDT
> > > To: hosking at cs.purdue.edu
> > > Subject: Returned mail: see transcript for details
> > >
> > > The original message was received at Sat, 11 Aug 2007 13:15:10
> > > -0400 (EDT)
> > > from daemon at localhost
> > >
> > > ----- The following addresses had permanent fatal errors -----
> > > jaykrell at verizon.net
> > >
> > > ----- Transcript of session follows -----
> > > ... while talking to relay.verizon.net.:
> > >>>> DATA
> > > <<< 550 4.2.1 mailbox temporarily disabled: jaykrell at verizon.net
> > > 550 5.1.1 jaykrell at verizon.net... User unknown
> > > <<< 554 5.5.0 No recipients have been specified.
> > > Reporting-MTA: dns; hermes50.mail.cornell.edu
> > > Arrival-Date: Sat, 11 Aug 2007 13:15:10 -0400 (EDT)
> > >
> > > Final-Recipient: RFC822; jaykrell at verizon.net
> > > Action: failed
> > > Status: 5.1.1
> > > Remote-MTA: DNS; relay.verizon.net
> > > Last-Attempt-Date: Sat, 11 Aug 2007 13:15:10 -0400 (EDT)
> > >
> > > From: Tony Hosking <hosking at cs.purdue.edu>
> > > Date: August 11, 2007 1:14:21 PM EDT
> > > To: <jay.krell at cornell.edu>
> > > Cc: Modula-3 developers <m3devel at elegosoft.com>,
> > > <m3commit at elegosoft.com>
> > > Subject: Re: [M3commit] CVS Update: cm3
> > >
> > >
> > > Did you rebuild the backend?
> > >
> > > I have built this on Darwin x86 and Linux x86 without problems.
> > >
> > > On Aug 11, 2007, at 1:06 PM, j k wrote:
> > >
> > >> I can build the compiler, but, youch, can't build m3core\long.m3:
> > >>
> > >> "..\src\word\Long.m3", line 11: Unknown type of size other than
> > >> dword in movOp
> > >>
> > >> The x86 back end needs work..I'll see if I can't just provide  
> this
> > >> stuff in C and avoid understanding the backend much..
> > >>
> > >> - Jay
> > >>
> >
>
>
> New home for Mom, no cleanup required. All starts here.
> Messenger Café — open for fun 24/7. Hot games, cool activities  
> served daily. Visit now.