[M3devel] LLVM backend?

[Dragiša Durić]

I've also skimmed through DWARF last year or something like that… _It is_ more complete than stabs and while (esp m3gdb) stabs are mostly hiding and guarding data from compiler through optimizer and linker to debugger, DWARF is made to enable modification of debug info as code is modified (esp while being optimized). There is no order of magnitude big enough to express its advantage over hacked-in-stabs.

--
Dragiša Durić
dragisha at m3w.org



On Mar 28, 2013, at 4:23 PM, Rodney M. Bates wrote:

> LLVM has a lot of already provided support for dwarf debug info, keeping it together with code,
> and helping to transform it in parallel with code, when optimizations, etc., are done.
> Meanwhile, dwarf itself is vastly more complete and appears to me, from superficial study,
> to be capable of representing all, or certainly most, of what is needed for good Modula-3 debugging.
> For these two reasons, I think LLVM plus dwarf present by far the best method to support
> a nice language-specific debugging experience, while leaving massive kludges behind.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20130330/b6a59a43/attachment-0002.html>