[M3devel] m3back directions?

[Tony Hosking]

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?

> 
> Olaf
> 
>> - 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
>> 
>> 
>> 
> 
>