<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
Do you mean to ask, am I embarassed that I nor any of us have done it ourselves by now?<BR>
Yes. :)<BR>
(Though I don't know about the question as stated.)<BR>
<BR>
<BR>
Interest level here is higher than I expected in non-gcc backends.<BR>
And Tony gave the answer I expected. :)<BR>
I don't know. It's kind of cheating, less fun, very hard to ramp up on, but once there very useful and good reuse and code quality.<BR>
So I'll consider this higher priority, if nobody beats me to it.<BR>
<BR>
<BR>
I also noticed the two burg backends in the 3.6 tree.<BR>
Did they build and work?<BR>
Eh, rhetorical mostly. It's hard to get one's head around this stuff.<BR>
Easier to improve m3back.<BR>
Though they had a MIPS backend too and I do have some MIPS machines.. (SGIs and router).<BR>
<BR>
<BR>
I'd like to first:<BR>
current release <BR>
CodeView debugging <BR>
test/optimize atomics (anyone can test this, please do) <BR>
test/fix 64bit range checks (anyone can test this, please do) <BR>
the micro optimizations I've been repeatedly describing (not multi pass, just "objfile.move") <BR>
And then once I have "move", fix the >4K frame bug. <BR>
And then I'll try to consider other x86 backends again. <BR>
<BR>
<BR>
- Jay<BR> <BR>> Date: Sat, 3 Apr 2010 18:41:31 -0500<BR>> From: rodney_bates@lcwb.coop<BR>> To: m3devel@elegosoft.com<BR>> Subject: Re: [M3devel] m3back directions?<BR>> <BR>> Wasn't it written an Montreal Poly as a student project or something?<BR>> <BR>> Jay K wrote:<BR>> > No, really. GPL.<BR>> > <BR>> > http://modula3.elegosoft.com/cgi-bin/cvsweb.cgi/pm3/m3/pm3/language/modula3/m3compiler/m3back/src/linux/Codex86.m3?rev=1.3;content-type=text%2Fplain<BR>> > <BR>> > http://modula3.elegosoft.com/cgi-bin/cvsweb.cgi/pm3/m3/pm3/language/modula3/m3compiler/m3objfile/src/linux/ELFObjFile.m3?rev=1.2;content-type=text%2Fplain<BR>> > <BR>> > - Jay<BR>> > <BR>> > <BR>> > ------------------------------------------------------------------------<BR>> > From: hosking@cs.purdue.edu<BR>> > Date: Thu, 1 Apr 2010 11:59:58 -0400<BR>> > To: jay.krell@cornell.edu<BR>> > CC: m3devel@elegosoft.com<BR>> > Subject: Re: [M3devel] m3back directions?<BR>> > <BR>> > All of PM3 is licensed the same way as CM3 (they both derive from the <BR>> > same DEC SRC sources).<BR>> > <BR>> > <BR>> > On 1 Apr 2010, at 08:33, Jay K wrote:<BR>> > <BR>> > I think it was GPL though.<BR>> > <BR>> > - Jay<BR>> > <BR>> > > Date: Thu, 1 Apr 2010 10:33:13 +0200<BR>> > > From: wagner@elegosoft.com <mailto:wagner@elegosoft.com><BR>> > > To: hosking@cs.purdue.edu <mailto:hosking@cs.purdue.edu><BR>> > > CC: m3devel@elegosoft.com <mailto:m3devel@elegosoft.com><BR>> > > Subject: Re: [M3devel] m3back directions?<BR>> > > <BR>> > > Quoting Tony Hosking <hosking@cs.purdue.edu<BR>> > <mailto:hosking@cs.purdue.edu>>:<BR>> > > <BR>> > > > On 31 Mar 2010, at 06:18, wagner@elegosoft.com<BR>> > <mailto:wagner@elegosoft.com> wrote:<BR>> > > ><BR>> > > >> Quoting Jay K <jay.krell@cornell.edu<BR>> > <mailto:jay.krell@cornell.edu>>:<BR>> > > >><BR>> > > >>> I'm curious what, if anything, people are interested in in m3back?<BR>> > > >>><BR>> > > >>> There are several mostly independent directions:<BR>> > > >>><BR>> > > >>> - remove it; use the gcc backend or other (burg, llvm, generate C)<BR>> > > >>><BR>> > > >>> - expand to support other targets, AMD64_*, including AMD64_NT<BR>> > > >>><BR>> > > >>> m3objfile would need macho/elf support for non-NT<BR>> > > >><BR>> > > >> It would be great if we could use the integrated backend for other<BR>> > > >> targets, too. Adding ELF support will be a lot of work, but<BR>> > it's probably<BR>> > > >> worth it.<BR>> > > ><BR>> > > > Have you looked at the pm3 Linux support?<BR>> > > <BR>> > > Indeed I had forgotten about that. I'll take at look at the Easter<BR>> > > holidays,<BR>> > > <BR>> > > Olaf<BR>> > > <BR>> > > <BR>> > <BR>> > <BR> </body>
</html>