<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>Actually it's slightly more real than I said.<BR>
One cm3.exe on Windows can do any of NT386/NT386GNU/NT386MINGNU. Sometimes it uses the "extra" code, sometimes not. These are in a sense a limited form of cross build. Granted, if it was only for those three psuedo platforms, you wouldn't mind.<BR>
<BR>
- Jay<BR><BR>
<BLOCKQUOTE>
<HR id=EC_stopSpelling>
From: jayk123@hotmail.com<BR>To: hosking@cs.purdue.edu; hosking@elego.de<BR>Date: Sat, 2 Feb 2008 00:12:27 +0000<BR>CC: m3devel@elegosoft.com<BR>Subject: Re: [M3devel] [M3commit] CVS Update: cm3<BR><BR>
<META content="Microsoft SafeHTML" name=Generator>
<STYLE>
.ExternalClass .EC_hmmessage P
{padding:0px;}
.ExternalClass EC_body.hmmessage
{font-size:10pt;font-family:Tahoma;}
</STYLE>
This was deliberate. It enables some cross-build scenarios. That I admit I haven't used (yet?), but I really like the idea.<BR> If m3linker were completed, then "full" cross builds would be real.<BR> <BR>The "extra" packages are small and build fast (well, at least not using cm3cg...).<BR>Is it <EM>really </EM>so onerous? Really?<BR> <BR>Isn't it nice to have less filtering of packages as well?<BR>Like, when you are building on non-NT386, you can easily see that you didn't break building on NT386, at least partly.<BR>?<BR> <BR> - Jay<BR><BR>
<HR id=EC_stopSpelling>
<BR>> From: hosking@cs.purdue.edu<BR>> Date: Fri, 1 Feb 2008 18:57:32 -0500<BR>> To: hosking@elego.de<BR>> CC: m3devel@elegosoft.com<BR>> Subject: Re: [M3devel] [M3commit] CVS Update: cm3<BR>> <BR>> I just checked in support for full declaration of paramters even on <BR>> imported procedures in the gcc-based backend. This is to support <BR>> proper generation of stdcall calling convention on Windows. In the <BR>> process of testing this I discovered that cm3 on non-Windows <BR>> platforms now needs to build and ship both of the Windows x86 support <BR>> libraries m3back and m3objfile, even though non-Windows platforms <BR>> don't use or need them. This seems broken to me. It seems that cm3 <BR>> has changed so that it now has these dependencies. Can we please <BR>> undo this? -- I see no need to have to build these for non-x86 <BR>> platforms that will never use them.<BR>> <BR>> On Feb 2, 2008, at 12:43 AM, Antony Hosking wrote:<BR>> <BR>> > CVSROOT: /usr/cvs<BR>> > Changes by: hosking@birch. 08/02/02 00:43:53<BR>> ><BR>> > Modified files:<BR>> > cm3/m3-sys/m3cc/gcc/gcc/m3cg/: parse.c<BR>> ><BR>> > Log message:<BR>> > Add parameter decls even for imported procedures, as per Jay <BR>> > Krell's request<BR>> > to support stdcall parameter passing mode on Windows.<BR>> <BR><BR><BR>
<HR>
Connect and share in new ways with Windows Live. <A href="http://www.windowslive.com/share.html?ocid=TXT_TAGHM_Wave2_sharelife_012008" target=_blank>Get it now!</A> </BLOCKQUOTE><br /><hr />Shed those extra pounds with MSN and The Biggest Loser! <a href='http://biggestloser.msn.com/' target='_new'>Learn more.</a></body>
</html>