[M3devel] m3back directions?

[Dragiša Durić]

It is started job and useable right now.

IMO - it's prolonged and thriving existence shows directions and
maintains secure interface for multiple backends - LLVM for example.

Thus said, my opinion is:
a) keep it, and make it excellent working x86 backend alternative.
b) AMD64, as natural successor to x86 - maybe, if it's not too much
work. Even without it - m3back can probably work for many x86 appliances
present - for years to come.
c) debug - of course it's good idea. But, if it's alternative, one can
debug her code using gcc, then switch to m3back build for productivity.
d) nothing too big of optimizations, although inlining would be sweet.

dd

On Wed, 2010-03-31 at 04:41 +0000, Jay K wrote:
> 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.
-- 
Dragiša Durić <dragisha at m3w.org>