<html>
<head>
<style>
P
{
margin:0px;
padding:0px
}
body
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body>I have the inclination, still working on time and expertise. :)<BR>
Summarize the layering for me? Which module calls which?<BR>Your mention below of the assumption of 32 bit ops at least confirms what I thought I vaguely understood reading through the source. It's just a bunch of pretty dense code without documentation, the sort I write myself when I have the whole program in my head and just need to type it all in as quickly as possible. Would the idea be to use a tagged union for this stack, or to split 64 bits ops into pairs of 32 bit ops?<BR>
You know, like, does this stack translate "closely" to the generated code, or not? If it does, pairs, if it does not, tagged union. Probably. Similarly, like, all the register dealings need some notion of pairs..? Maybe I should look at the other backend to understand better, if there is an analogous bunch of code.<BR>
<BR>
Anyway, I'll try at least this weekend to verify that it's buildable asis, i know that's just a teeny tiny baby step, just push the button to build, a monkey could do it... my expertise is beyond that, but...<BR>
<BR>
I suspect tagged union is it, and have to churn a bunch of code to check the type. ugh.<BR>
lots of "Is64" sprinkled, or GetSize (assuming some futuristic 128 bit type).<BR>
<BR>
??<BR>
<BR>
Thanks,<BR>
- Jay<BR><BR><BR>
<HR id=stopSpelling>
<BR>
> CC: m3devel@elegosoft.com<BR>> From: hosking@cs.purdue.edu<BR>> Subject: Re: Windows<BR>> Date: Thu, 16 Aug 2007 12:47:36 -0400<BR>> To: jay.krell@cornell.edu; jayk123@hotmail.com<BR>> <BR>> I should have realized of course that there is a very simple fix for <BR>> compilation on the NT386 target using the native m3back backend! <BR>> Simply make LONGINT=Int32. Jay, I have just checked in this very <BR>> simple fix to Target.m3 which should permit you to bootstrap a new <BR>> cm3 and compile the current CVS head.<BR>> <BR>> On Aug 16, 2007, at 9:42 AM, Tony Hosking wrote:<BR>> <BR>> > With the current native Windows backend (m3back) blindly assuming <BR>> > (without even checking!) that all integer operations are 32-bit, I <BR>> > wonder if anyone out there has the expertise, time, or inclination <BR>> > to smarten it up to handle both 32-bit and 64-bit ops. It should <BR>> > not be *too* hard, but I don't have the time for it now, though I <BR>> > would be happy to answer any questions that arise. Unfortunately, <BR>> > this reveals that Windows support is withering on the vine, in <BR>> > spite of Jay's excellent recent work. As of now, this means that <BR>> > Windows can only build CVS sources with the tag <BR>> > devel_LONGINT_start. Bridging the gap will require smartening up <BR>> > m3back or using the gcc-based backend.<BR>> ><BR>> <BR><BR><br /><hr />See what you’re getting into…before you go there <a href='http://newlivehotmail.com/?ocid=TXT_TAGHM_migration_HM_viral_preview_0507' target='_new'>See it!</a></body>
</html>