[M3devel] m3back directions?

[Tony Hosking]

On 31 Mar 2010, at 00:41, Jay K wrote:

> I'm curious what, if anything, people are interested in in m3back?

Simple. Fast.  It is target-dependent so optimising there is misguided effort unless the opts are target-dependent (instruction selection, register allocation!).  We don't have resources to maintain a sophisticated backend.  Better to rely on other tools.  There was a Linux version in pm3 that we should be able to model on.

> 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/2aac21d7/attachment-0002.html>