<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>Well that I can contradict. Digital (Bill Kalsow) did the x86 backend.<BR>Attached is from boot-LINUXELF.tar.bz2 (originally some other compression).<BR>
<BR>
2) Unpack "boot-XYZ.tar.gz":<BR>
gunzip < boot-XYZ.tar.gz | tar xpof -<BR>
3) Inside the boot-XYZ directory that gets created,<BR> unpack "m3cc.tar.gz". It's the gcc-based backend.<BR>
cd boot-XYZ<BR> gunzip < ../m3cc.tar.gz | tar xpof -<BR>
On Windows 95 and Windows NT, m3cc is not used. This step should<BR> be skipped.<BR>
<BR>
I think a C producing backend would be useful, to quickly get Windows IA64 and AMD64 support...<BR>
<BR> - Jay<BR><BR><BR>
<HR id=stopSpelling>
<BR>
> From: hosking@cs.purdue.edu<BR>> Date: Fri, 30 Nov 2007 09:12:23 -0500<BR>> To: jay.krell@cornell.edu<BR>> CC: m3devel@elegosoft.com<BR>> Subject: Re: [M3devel] non-gcc backend<BR>> <BR>> CMass (Bill Kalsow) were the ones to do the x86 backend I think.<BR>> <BR>> On Nov 30, 2007, at 2:28 AM, Jay wrote:<BR>> <BR>> > I thought the last Digital release used the non-gcc backend for <BR>> > Linux x86. My mistake I see.<BR>> > The next thing to look into is the Critical Mass release, which I <BR>> > can't get to at the moment.<BR>> ><BR>> > - Jay<BR><BR><br /><hr />Get the power of Windows + Web with the new Windows Live. <a href='http://www.windowslive.com?ocid=TXT_TAGLM_Wave2_powerofwindows_112007' target='_new'>Power up!</a></body>
</html>