Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!mips!decwrl!ucbvax!huji.ac.il!amoss
From: amoss@huji.ac.il (Amos Shapira)
Newsgroups: comp.lang.c++
Subject: Re: Porting cfront to MIPS
Message-ID: <amoss.651752813@shum>
Date: 27 Aug 90 10:26:53 GMT
References: <2533@ryn.esg.dec.com> <5606@abaa.UUCP>
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 22

liu.se> <10629@cadillac.CAD.MCC.COM> <2045@idunno.Princeton.EDU>
Sender: news@shum.huji.ac.il
Lines: 17
Apparently-To: post-usenet@ucbvax.berkeley.edu


Hello,
 I did a dirty port of cfront about a year ago. The compiler error
 seemed to be that the error reporting routine accessed the stack
 directly, and not through varargs, what I did was to avoid
 calling it. And it looks O.K. now. Maybe I'll fix it in the future
 by changing it ot use varargs (I didn't find varargs on the system
 then).

 Right now I finished porting G++ to the Iris, the libs compile
 but some of them die during the test (i.e. the test finds
 melfunctionning of some of the classes). Maybe you whould like to try
 this.

Hope this helps,
Amos Shapira
amoss@batata.huji.ac.il