<html><head><base href="x-msg://39/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br>
<br><div><div>On 31 Mar 2010, at 00:41, Jay K wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div class="hmmessage" style="font-size: 10pt; font-family: Verdana; ">I'm curious what, if anything, people are interested in in m3back?<br></div></span></blockquote><div><br></div><div>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.</div><br><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div class="hmmessage" style="font-size: 10pt; font-family: Verdana; ">There are several mostly independent directions:<br> - remove it; use the gcc backend or other (burg, llvm, generate C)<br> - expand to support other targets, AMD64_*, including AMD64_NT<br> m3objfile would need macho/elf support for non-NT<br> - expand to generate good debugging information for Microsoft debuggers<br> - various smaller/larger optimizations<br> 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.<br> <br> <br>I'm thinking for now of working on the debugging information.<br> <br> <br> - Jay<br> <br></div></span></blockquote></div><br></body></html>