<html>

<head>

<style><!--

.hmmessage P

{

margin:0px;

padding:0px

}

body.hmmessage

{

font-size: 10pt;

font-family:Verdana

}

--></style>

</head>

<body class='hmmessage'>

No, really. GPL.<BR>

<BR><A href="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">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</A><BR>

<BR><A href="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">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</A><BR>

 <BR>

 - Jay<BR><BR> <BR>

<HR id=stopSpelling>

From: hosking@cs.purdue.edu Date: Thu, 1 Apr 2010 11:59:58 -0400 To: jay.krell@cornell.edu CC: m3devel@elegosoft.com Subject: Re: [M3devel] m3back directions? <BASE>All of PM3 is licensed the same way as CM3 (they both derive from the same DEC SRC sources).

<DIV><BR><BR>

<DIV>

<DIV>On 1 Apr 2010, at 08:33, Jay K wrote:</DIV><BR class=ecxApple-interchange-newline>

<BLOCKQUOTE><SPAN style="TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: medium Helvetica; WHITE-SPACE: normal; LETTER-SPACING: normal; WORD-SPACING: 0px" class=ecxApple-style-span>

<DIV style="FONT-FAMILY: Verdana; FONT-SIZE: 10pt" class=ecxhmmessage>I think it was GPL though.<BR> <BR> - Jay<BR> <BR>> Date: Thu, 1 Apr 2010 10:33:13 +0200<BR>> From:<SPAN class=ecxApple-converted-space> </SPAN><A href="mailto:wagner@elegosoft.com">wagner@elegosoft.com</A><BR>> To:<SPAN class=ecxApple-converted-space> </SPAN><A href="mailto:hosking@cs.purdue.edu">hosking@cs.purdue.edu</A><BR>> CC:<SPAN class=ecxApple-converted-space> </SPAN><A href="mailto:m3devel@elegosoft.com">m3devel@elegosoft.com</A><BR>> Subject: Re: [M3devel] m3back directions?<BR>><SPAN class=ecxApple-converted-space> </SPAN><BR>> Quoting Tony Hosking <<A href="mailto:hosking@cs.purdue.edu">hosking@cs.purdue.edu</A>>:<BR>><SPAN class=ecxApple-converted-space> </SPAN><BR>> > On 31 Mar 2010, at 06:18,<SPAN class=ecxApple-converted-space> </SPAN><A href="mailto:wagner@elegosoft.com">wagner@elegosoft.com</A><SPAN class=ecxApple-converted-space> </SPAN>wrote:<BR>> ><BR>> >> Quoting Jay K <<A href="mailto:jay.krell@cornell.edu">jay.krell@cornell.edu</A>>:<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 it's probably<BR>> >> worth it.<BR>> ><BR>> > Have you looked at the pm3 Linux support?<BR>><SPAN class=ecxApple-converted-space> </SPAN><BR>> Indeed I had forgotten about that. I'll take at look at the Easter<BR>> holidays,<BR>><SPAN class=ecxApple-converted-space> </SPAN><BR>> Olaf<BR>><SPAN class=ecxApple-converted-space> </SPAN><BR>><SPAN class=ecxApple-converted-space> </SPAN><BR></DIV></SPAN></BLOCKQUOTE></DIV><BR></DIV>                                         </body>

</html>