<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>Wow that is crazy.<BR>
The "OS" is backwards compatible.<BR>
The tools -- or at least the headers/libs -- are not backwards compatible.<BR>
They apparently don't produce binaries that run on older systems.<BR>
<BR>
Hm, so I did some diffing among<BR>m3-libs\m3core\src\unix\freebsd-*<BR>
they are all amost identical.<BR>and almost all compatible.<BR>Freebsd-1 to -2 is the least compatible.<BR>otherwise the only actual difference I see is<BR> in Usignal sa_flags and sa_mask getting reversed.<BR> and sigcontext changed.<BR>
<BR>Otherwise it's mostly things like long vs. unsigned_long,<BR>int64_t vs. quad_t, short vs. int16_t.<BR>
<BR>The DIR record grew, but as long as it is not implemented<BR>in Modula-3 and the new fields not access, no matter.<BR>
Oh one errno value changed.<BR>
Sometimes some types or functions got added, but<BR> that is ok.<BR>
<BR>
Maybe more research at a might later date...<BR>
<BR>
- Jay<BR><BR><BR>
<HR id=stopSpelling>
<BR>
> To: jayk123@hotmail.com<BR>> CC: m3devel@elegosoft.com<BR>> Subject: Re: [M3devel] which platforms? and questions about FreeBSD versioning <BR>> Date: Thu, 15 May 2008 22:54:28 -0700<BR>> From: mika@async.caltech.edu<BR>> <BR>> <BR>> No, sorry, haven't gotten around to testing the current NT386GNU<BR>> cm3... I have a lot of version synchronizing to do, unfortunately :(<BR>> <BR>> Yes, FreeBSD is backwards-compatible, *not* forwards-compatible.<BR>> That is, you can build even fairly complex software packages on an old<BR>> FreeBSD system and expect it to run on the latest release. You cannot,<BR>> as a general rule, build anything on a newer system and expect it to work<BR>> on an older one. There must be "some" way of doing it that way, but<BR>> I don't know what it is, and I don't know if it's very well supported.<BR>> I keep FreeBSD 4.x systems around for precisely this reason: the binaries<BR>> compiled there work fine on 5.x and 6.x (as far as I have tested). Not<BR>> the other way around! In fact it has never worked the other way, as <BR>> long as I can remember, with FreeBSD.<BR>> <BR>> This is also why I suggest that a "FreeBSD4" bootstrap should actually<BR>> be built on FreeBSD 4.x and not 5.x, 6.x, or 7.x!<BR>> <BR>> Mika<BR>> <BR>> Jay writes:<BR>> >--_14c076c4-fb7c-48b0-b705-2e38d4b4a333_<BR>> >Content-Type: text/plain; charset="iso-8859-1"<BR>> >Content-Transfer-Encoding: quoted-printable<BR>> ><BR>> >Mika, ok, this is tangential: Have you tried the current NT386GNU cm3?<BR>> >=20<BR>> >I meant, more about what "operating systems" that Modula-3 does not support=<BR>> > do people here use, would like to see Modula-3 on. Or maybe I meant both.<BR>> >=20<BR>> >Speaking of the "4" in FreeBSD4:<BR>> >=20<BR>> >Has FreeBSD, and the other BSDs, really broken backward compat?<BR>> >They really change interfaces a lot such that binaries built with current h=<BR>> >eaders/libs won't run on older versions?<BR>> >And there isn't an easy way on current platforms to build something using o=<BR>> >lder tools to run on older and newer platforms?<BR>> >Look at Windows for example. If you call a "new" function directly, you wil=<BR>> >l fail to load on older platforms. So either don't call them, or use LoadLi=<BR>> >brary/GetProcAddress. Structures almost never change size, though there is =<BR>> >some screwiness there, stuff like:<BR>> >=20<BR>> >struct FOO { size_t Size;<BR>> > int Field1;<BR>> >#if VERSION > 1234<BR>> > int Field2;<BR>> >#endif<BR>> >};<BR>> >=20<BR>> >I think it should be more like:<BR>> >=20<BR>> >struct FOO { size_t Size;<BR>> > int Field1;<BR>> >#if VERSION > 1234<BR>> > int Field2;<BR>> >#endif<BR>> >};<BR>> >=20<BR>> >struct FOO_V1{ size_t Size;<BR>> > int Field1;<BR>> >};<BR>> >=20<BR>> >struct FOO_V2 { size_t Size;<BR>> > int Field1;<BR>> > int Field2;<BR>> >};<BR>> >=20<BR>> >#if VERSION > 1234<BR>> >typedef FOO_V2 FOO;<BR>> >#else<BR>> >typedef FOO_V1 FOO;<BR>> >#endif<BR>> >=20<BR>> >I understand that binaries built on the older platform will continue to wor=<BR>> >k on the newer platform.<BR>> >That is one thing.<BR>> >But it is also useful to be able to build binaries on the newer platform th=<BR>> >at will on the older platform.<BR>> >Apple also invests a bunch here.<BR>> >=20<BR>> >Well, ok, if it was really "bad", there'd be FreeBSD5, 6, 7.<BR>> >I guess maybe they broke this stuff sometimes but haven't in a while?<BR>> >That you can build FreeBSD4 binaries on FreeBSD7 and the run down to 4?<BR>> >=20<BR>> >And then, same questions about OpenBSD and NetBSD.<BR>> >I understand -- I could/must go and install a bajillion operating systems a=<BR>> >nd test and find out, but I don't expect to spend the time that way and pus=<BR>> >h comes to shove, any BSD (and Linux, Solaris, NT, CE, etc.) variants I int=<BR>> >roduce will have no version number in them, will be built on whatever I hav=<BR>> >e, and it will be unknown if they work on older. And maybe something will m=<BR>> >aterialize to be more portable, like interfacing to the Posix via C instead=<BR>> > of cloned headers.<BR>> >=20<BR>> > - Jay<BR>> ><BR>> ><BR>> ><BR>> >> To: jayk123@hotmail.com> CC: m3devel@elegosoft.com> Subject: Re: [M3devel=<BR>> >] which platforms? > Date: Thu, 15 May 2008 14:30:36 -0700> From: mika@asyn=<BR>> >c.caltech.edu> > here it is:> > FreeBSD4> PPC_DARWIN> NT386GNU> LINUXLIBC6>=<BR>> > > I386_DARWIN coming soon> > Tony Hosking writes:> >> >--Apple-Mail-4-6310=<BR>> >28010> >Content-Type: text/plain;> > charset=3DUS-ASCII;> > format=3Dflowed=<BR>> >;> > delsp=3Dyes> >Content-Transfer-Encoding: 7bit> >> >SOLgnu> >PPC_DARWIN=<BR>> >> >I386_DARWIN> >AMD64_DARWIN> >LINUXLIBC6> >I'd like AMD64_LINUX, SPARC64_=<BR>> >SOLARISN but no time right now to devote > >to them.> >> >On May 14, 2008, =<BR>> >at 1:25 PM, Jay wrote:> >> >> What do people run?> >> In particular: NetBSD=<BR>> >? OpenBSD? Sparc32? Sparc64? PPC64_DARWIN? > >> I386_SOLARIS? AMD64_SOLARIS=<BR>> >? SPARC64_SOLARIS? ARM_WINCE? AMD64_NT?> >>> >> Just curious, I'll probably=<BR>> > bring up whatever I can, it's fun, and > >> yes, get back and fix AMD64_LI=<BR>> >NUX to have> >> garbage collection, NT386GNU and NT386 tests, cross-platfor=<BR>> >m sets, > >> setup some Tinderboxes, etc...> >>> >> (AMD64_NT: the gcc avai=<BR>> >lable for this includes a bunch of patches, > >> so I'm inclined to either =<BR>> >wait for them to go upstream,> >> or seek an alternate route such as "port"=<BR>> > the in-proc backend, llvm, > >> generate C, or maybe write an interpreter =<BR>> >for the IL;> >> and "porting" the backend is probably best preceded by a) x=<BR>> >86 > >> LONGINT support b) other x86 targets "for practise", at least one,>=<BR>> > >> though regarding .obj file formats, that would be tangential.)> >>> >> =<BR>> >- Jay> >>> >>> >>> >>> >> >> >--Apple-Mail-4-631028010> >Content-Type: text=<BR>> >/html;> > charset=3DUS-ASCII> >Content-Transfer-Encoding: quoted-printable>=<BR>> > >> ><html><body style=3D3D"word-wrap: break-word; -webkit-nbsp-mode: space=<BR>> >; =3D> >-webkit-line-break: after-white-space; "><div =3D> >apple-content-e=<BR>> >dited=3D3D"true"><span class=3D3D"Apple-style-span" =3D> >style=3D3D"border=<BR>> >-collapse: separate; border-spacing: 0px 0px; color: =3D> >rgb(0, 0, 0); fo=<BR>> >nt-family: Helvetica; font-size: 12px; font-style: =3D> >normal; font-varia=<BR>> >nt: normal; font-weight: normal; letter-spacing: =3D> >normal; line-height:=<BR>> > normal; text-align: auto; =3D> >-khtml-text-decorations-in-effect: none; t=<BR>> >ext-indent: 0px; =3D> >-apple-text-size-adjust: auto; text-transform: none;=<BR>> > orphans: 2; =3D> >white-space: normal; widows: 2; word-spacing: 0px; "><di=<BR>> >v =3D> >style=3D3D"word-wrap: break-word; -khtml-nbsp-mode: space; =3D> >-k=<BR>> >html-line-break: after-white-space; "><span class=3D3D"Apple-style-span" =<BR>> >=3D> >style=3D3D"border-collapse: separate; border-spacing: 0px 0px; color:=<BR>> > =3D> >rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =<BR>> >=3D> >normal; font-variant: normal; font-weight: normal; letter-spacing: =<BR>> >=3D> >normal; line-height: normal; text-align: auto; =3D> >-khtml-text-deco=<BR>> >rations-in-effect: none; text-indent: 0px; =3D> >-apple-text-size-adjust: a=<BR>> >uto; text-transform: none; orphans: 2; =3D> >white-space: normal; widows: 2=<BR>> >; word-spacing: 0px; =3D> >">SOLgnu</span></div><div style=3D3D"word-wrap: =<BR>> >break-word; =3D> >-khtml-nbsp-mode: space; -khtml-line-break: after-white-s=<BR>> >pace; =3D> >">PPC_DARWIN</div><div style=3D3D"word-wrap: break-word; -khtml=<BR>> >-nbsp-mode: =3D> >space; -khtml-line-break: after-white-space; ">I386_DARWI=<BR>> >N</div><div =3D> >style=3D3D"word-wrap: break-word; -khtml-nbsp-mode: space=<BR>> >; =3D> >-khtml-line-break: after-white-space; ">AMD64_DARWIN</div><div =3D>=<BR>> > >style=3D3D"word-wrap: break-word; -khtml-nbsp-mode: space; =3D> >-khtml-l=<BR>> >ine-break: after-white-space; ">LINUXLIBC6</div><div =3D> >style=3D3D"word-=<BR>> >wrap: break-word; -khtml-nbsp-mode: space; =3D> >-khtml-line-break: after-w=<BR>> >hite-space; ">I'd like AMD64_LINUX, <span =3D> >class=3D3D"Apple-style=<BR>> >-span" style=3D3D"font-family: Tahoma; font-size: =3D> >13px; ">SPARC64_SOL=<BR>> >ARISN but no time right now to devote to =3D> >them.</span></div></span></d=<BR>> >iv><br><div><div>On May 14, 2008, at 1:25 =3D> >PM, Jay wrote:</div><br cla=<BR>> >ss=3D3D"Apple-interchange-newline"><blockquote =3D> >type=3D3D"cite"><span =<BR>> >class=3D3D"Apple-style-span" style=3D3D"border-collapse: =3D> >separate; co=<BR>> >lor: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; =3D> >font-styl=<BR>> >e: normal; font-variant: normal; font-weight: normal; =3D> >letter-spacing:=<BR>> > normal; line-height: normal; orphans: 2; text-align: =3D> >auto; text-inde=<BR>> >nt: 0px; text-transform: none; white-space: normal; =3D> >widows: 2; word-s=<BR>> >pacing: 0px; -webkit-border-horizontal-spacing: 0px; =3D> >-webkit-border-v=<BR>> >ertical-spacing: 0px; =3D> >-webkit-text-decorations-in-effect: none; -webk=<BR>> >it-text-size-adjust: =3D> >auto; -webkit-text-stroke-width: 0; "><div class=<BR>> >=3D3D"hmmessage" =3D> >style=3D3D"font-size: 10pt; font-family: Tahoma; ">W=<BR>> >hat do people =3D> >run?<br>In particular: NetBSD? OpenBSD? Sparc32? Sparc6=<BR>> >4? PPC64_DARWIN? =3D> >I386_SOLARIS? AMD64_SOLARIS? SPARC64_SOLARIS? ARM_WI=<BR>> >NCE? =3D> >AMD64_NT?<br> <br>Just curious, I'll probably bring up what=<BR>> >ever I =3D> >can, it's fun, and yes, get back and fix AMD64_LINUX to have<b=<BR>> >r>garbage =3D> >collection, NT386GNU and NT386 tests, cross-platform s=<BR>> >ets, setup =3D> >some Tinderboxes, etc...<br> <br>(AMD64_NT: the gcc a=<BR>> >vailable for =3D> >this includes a bunch of patches, so I'm inclined to eit=<BR>> >her wait for =3D> >them to go upstream,<br>or seek an alternate route such =<BR>> >as "port" the =3D> >in-proc backend, llvm, generate C, or maybe write an in=<BR>> >terpreter for the =3D> >IL;<br>and "porting" the backend is probably best p=<BR>> >receded by a) x86 =3D> >LONGINT support b) other x86 targets "for practise"=<BR>> >, at least =3D> >one,<br>though regarding .obj file formats, that would be =<BR>> >=3D> >tangential.)<br> <br> - =3D> >Jay<br><br><br><br><br></div>=<BR>> ></span></blockquote></div><br></body></html>=3D> >> >--Apple-Mail-4-6310280=<BR>> >10--=<BR>> ><BR>> >--_14c076c4-fb7c-48b0-b705-2e38d4b4a333_<BR>> >Content-Type: text/html; charset="iso-8859-1"<BR>> >Content-Transfer-Encoding: quoted-printable<BR>> ><BR>> ><html><BR>> ><head><BR>> ><style><BR>> >.hmmessage P<BR>> >{<BR>> >margin:0px;<BR>> >padding:0px<BR>> >}<BR>> >body.hmmessage<BR>> >{<BR>> >FONT-SIZE: 10pt;<BR>> >FONT-FAMILY:Tahoma<BR>> >}<BR>> ></style><BR>> ></head><BR>> ><body class=3D'hmmessage'>Mika, ok, this is tangential: Have you =<BR>> >tried the current NT386GNU cm3?<BR><BR>> > <BR><BR>> >I meant, more about what "operating systems" that Modula-3 does not support=<BR>> > do people here use, would like to see Modula-3 on. Or maybe I meant both.<=<BR>> >BR><BR>> > <BR><BR>> >Speaking of the "4" in FreeBSD4:<BR><BR>> > <BR><BR>> >Has FreeBSD, and the other BSDs, really broken backward compat?<BR><BR>> >They really change interfaces a lot such that binaries built with current h=<BR>> >eaders/libs won't run on older versions?<BR><BR>> >And there isn't an easy way on current platforms to build something using o=<BR>> >lder tools to run on older and newer platforms?<BR><BR>> >Look at Windows for example. If you call a "new" function directly, you wil=<BR>> >l fail to load on older platforms. So either don't call them, or use LoadLi=<BR>> >brary/GetProcAddress. Structures almost never change size, though there is =<BR>> >some screwiness there, stuff like:<BR><BR>> > <BR><BR>> >struct FOO {<BR> size_t Size;<BR><BR>> > int Field1;<BR><BR>> >#if VERSION > 1234<BR><BR>> > int Field2;<BR><BR>> >#endif<BR><BR>> >};<BR><BR>> > <BR><BR>> >I think it should be more like:<BR><BR>> > <BR><BR>> >struct FOO {<BR> size_t Size;<BR><BR>> > int Field1;<BR><BR>> >#if VERSION > 1234<BR><BR>> > int Field2;<BR><BR>> >#endif<BR><BR>> >};<BR><BR>> > <BR><BR>> >struct FOO_V1{<BR> size_t Size;<BR><BR>> > int Field1;<BR><BR>> >};<BR><BR>> > <BR><BR>> >struct FOO_V2 {<BR> size_t Size;<BR><BR>> > int Field1;<BR><BR>> > int Field2;<BR><BR>> >};<BR><BR>> > <BR><BR>> >#if VERSION > 1234<BR><BR>> >typedef FOO_V2 FOO;<BR><BR>> >#else<BR><BR>> >typedef FOO_V1 FOO;<BR><BR>> >#endif<BR><BR>> > <BR><BR>> >I understand that binaries built on the older platform will continue to wor=<BR>> >k on the newer platform.<BR><BR>> >That is one thing.<BR><BR>> >But it is also useful to be able to build binaries on the newer platform th=<BR>> >at will on the older platform.<BR><BR>> >Apple also invests a bunch here.<BR><BR>> > <BR><BR>> >Well, ok, if it was really "bad", there'd be FreeBSD5, 6, 7.<BR><BR>> >I guess maybe they broke this stuff sometimes but haven't in a while?<BR><BR>> >That you can build FreeBSD4 binaries on FreeBSD7 and the run down to 4?<BR><BR>> > <BR><BR>> >And then, same questions about OpenBSD and NetBSD.<BR><BR>> >I understand -- I could/must go and install a bajillion operating systems a=<BR>> >nd test and find out, but I don't expect to spend the time that way and pus=<BR>> >h comes to shove, any BSD (and Linux, Solaris, NT, CE, etc.) variants I int=<BR>> >roduce will have no version number in them, will be built on whatever I hav=<BR>> >e, and it will be unknown if they work on older. And maybe something will m=<BR>> >aterialize to be more portable, like interfacing to the Posix via C instead=<BR>> > of cloned headers.<BR><BR>> > <BR><BR>> > - Jay<BR><BR><BR><BR>> ><BR>> ><HR id=3DstopSpelling><BR>> ><BR><BR>> >> To: jayk123@hotmail.com<BR>> CC: m3devel@elegosoft.com<BR>> Subj=<BR>> >ect: Re: [M3devel] which platforms? <BR>> Date: Thu, 15 May 2008 14:30:3=<BR>> >6 -0700<BR>> From: mika@async.caltech.edu<BR>> <BR>> here it is:<B=<BR>> >R>> <BR>> FreeBSD4<BR>> PPC_DARWIN<BR>> NT386GNU<BR>> LINUXL=<BR>> >IBC6<BR>> <BR>> I386_DARWIN coming soon<BR>> <BR>> Tony Hosking=<BR>> > writes:<BR>> ><BR>> >--Apple-Mail-4-631028010<BR>> >Cont=<BR>> >ent-Type: text/plain;<BR>> > charset=3DUS-ASCII;<BR>> > format=<BR>> >=3Dflowed;<BR>> > delsp=3Dyes<BR>> >Content-Transfer-Encoding: =<BR>> >7bit<BR>> ><BR>> >SOLgnu<BR>> >PPC_DARWIN<BR>> >I38=<BR>> >6_DARWIN<BR>> >AMD64_DARWIN<BR>> >LINUXLIBC6<BR>> >I'd li=<BR>> >ke AMD64_LINUX, SPARC64_SOLARISN but no time right now to devote <BR>> &=<BR>> >gt;to them.<BR>> ><BR>> >On May 14, 2008, at 1:25 PM, Jay wrote=<BR>> >:<BR>> ><BR>> >> What do people run?<BR>> >> In par=<BR>> >ticular: NetBSD? OpenBSD? Sparc32? Sparc64? PPC64_DARWIN? <BR>> >>=<BR>> > I386_SOLARIS? AMD64_SOLARIS? SPARC64_SOLARIS? ARM_WINCE? AMD64_NT?<BR>>=<BR>> > >><BR>> >> Just curious, I'll probably bring up whatever I =<BR>> >can, it's fun, and <BR>> >> yes, get back and fix AMD64_LINUX to h=<BR>> >ave<BR>> >> garbage collection, NT386GNU and NT386 tests, cross-pl=<BR>> >atform sets, <BR>> >> setup some Tinderboxes, etc...<BR>> >&=<BR>> >gt;<BR>> >> (AMD64_NT: the gcc available for this includes a bunch=<BR>> > of patches, <BR>> >> so I'm inclined to either wait for them to g=<BR>> >o upstream,<BR>> >> or seek an alternate route such as "port" the =<BR>> >in-proc backend, llvm, <BR>> >> generate C, or maybe write an inte=<BR>> >rpreter for the IL;<BR>> >> and "porting" the backend is probably =<BR>> >best preceded by a) x86 <BR>> >> LONGINT support b) other x86 targ=<BR>> >ets "for practise", at least one,<BR>> >> though regarding .obj fi=<BR>> >le formats, that would be tangential.)<BR>> >><BR>> >> - =<BR>> >Jay<BR>> >><BR>> >><BR>> >><BR>> >><BR>=<BR>> >> ><BR>> ><BR>> >--Apple-Mail-4-631028010<BR>> >Con=<BR>> >tent-Type: text/html;<BR>> > charset=3DUS-ASCII<BR>> >Content-T=<BR>> >ransfer-Encoding: quoted-printable<BR>> ><BR>> ><html><=<BR>> >;body style=3D3D"word-wrap: break-word; -webkit-nbsp-mode: space; =3D<BR>&g=<BR>> >t; >-webkit-line-break: after-white-space; "><div =3D<BR>> >=<BR>> >apple-content-edited=3D3D"true"><span class=3D3D"Apple-style-span" =<BR>> >=3D<BR>> >style=3D3D"border-collapse: separate; border-spacing: 0px 0=<BR>> >px; color: =3D<BR>> >rgb(0, 0, 0); font-family: Helvetica; font-size:=<BR>> > 12px; font-style: =3D<BR>> >normal; font-variant: normal; font-weigh=<BR>> >t: normal; letter-spacing: =3D<BR>> >normal; line-height: normal; tex=<BR>> >t-align: auto; =3D<BR>> >-khtml-text-decorations-in-effect: none; tex=<BR>> >t-indent: 0px; =3D<BR>> >-apple-text-size-adjust: auto; text-transfor=<BR>> >m: none; orphans: 2; =3D<BR>> >white-space: normal; widows: 2; word-s=<BR>> >pacing: 0px; "><div =3D<BR>> >style=3D3D"word-wrap: break-word;=<BR>> > -khtml-nbsp-mode: space; =3D<BR>> >-khtml-line-break: after-white-sp=<BR>> >ace; "><span class=3D3D"Apple-style-span" =3D<BR>> >style=3D3D"=<BR>> >border-collapse: separate; border-spacing: 0px 0px; color: =3D<BR>> >=<BR>> >rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =3D<BR>&=<BR>> >gt; >normal; font-variant: normal; font-weight: normal; letter-spacing: =<BR>> >=3D<BR>> >normal; line-height: normal; text-align: auto; =3D<BR>> =<BR>> >>-khtml-text-decorations-in-effect: none; text-indent: 0px; =3D<BR>> =<BR>> >>-apple-text-size-adjust: auto; text-transform: none; orphans: 2; =3D<BR=<BR>> >>> >white-space: normal; widows: 2; word-spacing: 0px; =3D<BR>> &g=<BR>> >t;">SOLgnu</span></div><div style=3D3D"word-wrap: break-w=<BR>> >ord; =3D<BR>> >-khtml-nbsp-mode: space; -khtml-line-break: after-whit=<BR>> >e-space; =3D<BR>> >">PPC_DARWIN</div><div style=3D3D"word=<BR>> >-wrap: break-word; -khtml-nbsp-mode: =3D<BR>> >space; -khtml-line-bre=<BR>> >ak: after-white-space; ">I386_DARWIN</div><div =3D<BR>> >=<BR>> >style=3D3D"word-wrap: break-word; -khtml-nbsp-mode: space; =3D<BR>> >=<BR>> >-khtml-line-break: after-white-space; ">AMD64_DARWIN</div><div =<BR>> >=3D<BR>> >style=3D3D"word-wrap: break-word; -khtml-nbsp-mode: space; =<BR>> >=3D<BR>> >-khtml-line-break: after-white-space; ">LINUXLIBC6</d=<BR>> >iv><div =3D<BR>> >style=3D3D"word-wrap: break-word; -khtml-nbsp=<BR>> >-mode: space; =3D<BR>> >-khtml-line-break: after-white-space; ">I'=<BR>> >d like AMD64_LINUX,&nbsp;<span =3D<BR>> >class=3D3D"Apple-styl=<BR>> >e-span" style=3D3D"font-family: Tahoma; font-size: =3D<BR>> >13px; "&=<BR>> >gt;SPARC64_SOLARISN but no time right now to devote to =3D<BR>> >them=<BR>> >.</span></div></span></div><br><div><=<BR>> >;div>On May 14, 2008, at 1:25 =3D<BR>> >PM, Jay wrote:</div>=<BR>> ><br class=3D3D"Apple-interchange-newline"><blockquote =3D<BR>> =<BR>> >>type=3D3D"cite"><span class=3D3D"Apple-style-span" style=3D3D"bor=<BR>> >der-collapse: =3D<BR>> >separate; color: rgb(0, 0, 0); font-family: H=<BR>> >elvetica; font-size: 12px; =3D<BR>> >font-style: normal; font-variant=<BR>> >: normal; font-weight: normal; =3D<BR>> >letter-spacing: normal; line=<BR>> >-height: normal; orphans: 2; text-align: =3D<BR>> >auto; text-indent:=<BR>> > 0px; text-transform: none; white-space: normal; =3D<BR>> >widows: 2;=<BR>> > word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =3D<BR>> >=<BR>> >;-webkit-border-vertical-spacing: 0px; =3D<BR>> >-webkit-text-decorat=<BR>> >ions-in-effect: none; -webkit-text-size-adjust: =3D<BR>> >auto; -webk=<BR>> >it-text-stroke-width: 0; "><div class=3D3D"hmmessage" =3D<BR>> >=<BR>> >;style=3D3D"font-size: 10pt; font-family: Tahoma; ">What do people =3D<B=<BR>> >R>> >run?<br>In particular: NetBSD? OpenBSD? Sparc32? Sparc64? =<BR>> >PPC64_DARWIN? =3D<BR>> >I386_SOLARIS? AMD64_SOLARIS? SPARC64_SOLARIS?=<BR>> > ARM_WINCE? =3D<BR>> >AMD64_NT?<br>&nbsp;<br>Just cur=<BR>> >ious, I'll probably bring up whatever I =3D<BR>> >can, it's fun, and =<BR>> >yes, get back and fix AMD64_LINUX to have<br>garbage =3D<BR>> >=<BR>> >collection, NT386GNU and NT386 tests,&nbsp;cross-platform sets, setup =<BR>> >=3D<BR>> >some Tinderboxes, etc...<br>&nbsp;<br>(AMD6=<BR>> >4_NT: the gcc available for =3D<BR>> >this includes a bunch of patche=<BR>> >s, so I'm inclined to either wait for =3D<BR>> >them to go upstream,&=<BR>> >lt;br>or seek an alternate route such as "port" the =3D<BR>> >in-p=<BR>> >roc backend, llvm, generate C, or maybe write an interpreter for the =3D<BR=<BR>> >>> >IL;<br>and "porting" the backend is probably best preceded =<BR>> >by a) x86 =3D<BR>> >LONGINT support b) other x86 targets "for practis=<BR>> >e", at least =3D<BR>> >one,<br>though regarding .obj file forma=<BR>> >ts, that would be =3D<BR>> >tangential.)<br>&nbsp;<br>=<BR>> >;&nbsp;- =3D<BR>> >Jay<br><br><br><br><=<BR>> >;br></div></span></blockquote></div><br>&l=<BR>> >t;/body></html>=3D<BR>> ><BR>> >--Apple-Mail-4-6310280=<BR>> >10--<BR><BR></body><BR>> ></html>=<BR>> ><BR>> >--_14c076c4-fb7c-48b0-b705-2e38d4b4a333_--<BR><BR></body>
</html>