[M3devel] m3back directions?

[Jay K]

No, really. GPL.


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/m3objfile/src/linux/ELFObjFile.m3?rev=1.2;content-type=text%2Fplain

 

 - Jay

 


From: hosking at cs.purdue.edu
Date: Thu, 1 Apr 2010 11:59:58 -0400
To: jay.krell at cornell.edu
CC: m3devel at elegosoft.com
Subject: Re: [M3devel] m3back directions?

All of PM3 is licensed the same way as CM3 (they both derive from the same DEC SRC sources).




On 1 Apr 2010, at 08:33, Jay K wrote:

I think it was GPL though.
 
 - Jay
 
> Date: Thu, 1 Apr 2010 10:33:13 +0200
> From: wagner at elegosoft.com
> To: hosking at cs.purdue.edu
> CC: m3devel at elegosoft.com
> Subject: Re: [M3devel] m3back directions?
> 
> Quoting Tony Hosking <hosking at cs.purdue.edu>:
> 
> > On 31 Mar 2010, at 06:18, wagner at elegosoft.com wrote:
> >
> >> Quoting Jay K <jay.krell at cornell.edu>:
> >>
> >>> I'm curious what, if anything, people are interested in in m3back?
> >>>
> >>> There are several mostly independent directions:
> >>>
> >>> - remove it; use the gcc backend or other (burg, llvm, generate C)
> >>>
> >>> - expand to support other targets, AMD64_*, including AMD64_NT
> >>>
> >>> m3objfile would need macho/elf support for non-NT
> >>
> >> It would be great if we could use the integrated backend for other
> >> targets, too. Adding ELF support will be a lot of work, but it's probably
> >> worth it.
> >
> > Have you looked at the pm3 Linux support?
> 
> Indeed I had forgotten about that. I'll take at look at the Easter
> holidays,
> 
> Olaf
> 
> 

 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20100403/e3b3ae8a/attachment-0002.html>