[M3devel] m3back directions?

[Jay K]

 > remove it?


Oops, did I say that? :)

 


Well, we should definitely do some of the others if are going to keep it. :)


I'm leaning toward Microsoft CodeView debugging information currently.
It should be the easiest and provide a lot of value.
  Though it is actually in m3objfile.

 


I forgot to mention:
  It is already I think very portable to all 32bit x86 platforms.
  The real work work would be in m3objfile.
  A little in m3back regarding calling conventions perhaps.


Maybe a little around munging function names for "-shared -fPIC" too.
Like appending "@plt" in function calls or somesuch.


 - Jay



 
> Date: Wed, 31 Mar 2010 12:18:30 +0200
> From: wagner at elegosoft.com
> To: m3devel at elegosoft.com
> Subject: Re: [M3devel] m3back directions?
> 
> 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.
> 
> 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
> >
> >
> >
> 
> 
> 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20100331/d9fc0f4e/attachment-0002.html>