<html><head><base href="x-msg://136/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">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="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div class="hmmessage" style="font-size: 10pt; font-family: Verdana; ">I think it was GPL though.<br> <br> - Jay<br> <br>> Date: Thu, 1 Apr 2010 10:33:13 +0200<br>> From:<span class="Apple-converted-space"> </span><a href="mailto:wagner@elegosoft.com">wagner@elegosoft.com</a><br>> To:<span class="Apple-converted-space"> </span><a href="mailto:hosking@cs.purdue.edu">hosking@cs.purdue.edu</a><br>> CC:<span class="Apple-converted-space"> </span><a href="mailto:m3devel@elegosoft.com">m3devel@elegosoft.com</a><br>> Subject: Re: [M3devel] m3back directions?<br>><span class="Apple-converted-space"> </span><br>> Quoting Tony Hosking <<a href="mailto:hosking@cs.purdue.edu">hosking@cs.purdue.edu</a>>:<br>><span class="Apple-converted-space"> </span><br>> > On 31 Mar 2010, at 06:18,<span class="Apple-converted-space"> </span><a href="mailto:wagner@elegosoft.com">wagner@elegosoft.com</a><span class="Apple-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="Apple-converted-space"> </span><br>> Indeed I had forgotten about that. I'll take at look at the Easter<br>> holidays,<br>><span class="Apple-converted-space"> </span><br>> Olaf<br>><span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br></div></span></blockquote></div><br></div></body></html>