[M3devel] m3back directions?

[Jay K]

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

 - expand to generate good debugging information for Microsoft debuggers

 - various smaller/larger optimizations

    inlining? Inlining seems like the most lacking optimization and thinking about it, it doesn't actually seem that hard to do, at least a little bit.

 

 

I'm thinking for now of working on the debugging information.

 

 

 - Jay

 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20100331/19d41720/attachment-0001.html>