Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!news.iecc.com!.POSTED!nerds-end From: =?UTF-8?B?QyBCZXJnc3Ryw7Zt?= Newsgroups: comp.compilers Subject: Re: ELF and DWARF tools ? Date: Mon, 29 Dec 2014 13:22:23 +0700 Organization: Compilers Central Lines: 24 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <14-12-006@comp.compilers> References: <14-12-005@comp.compilers> NNTP-Posting-Host: news.iecc.com Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: miucha.iecc.com 1419872349 60537 2001:470:1f07:1126:0:676f:7373:6970 (29 Dec 2014 16:59:09 GMT) X-Complaints-To: abuse@iecc.com NNTP-Posting-Date: Mon, 29 Dec 2014 16:59:09 +0000 (UTC) Keywords: tools, LLVM Posted-Date: 29 Dec 2014 11:59:09 EST X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Xref: csiph.com comp.compilers:1449 On Mon, Dec 29, 2014 at 12:42 PM, John R. Levine wrote: > > I am working on a project which involves building a compiler toolchain for > yet another architecture. The obvious object format to use is ELF and > DWARF, and I'm trying to figure out the least painful way to do that. ... The llvm family of code is becoming more complete in terms of a full GNU replacement. That isn't the land of python, but you're going to have to go outside of that anyway for actual compiler/toolchain work. (LLVM has a builtin DWARF parser) I'm not a fan of llvm, but the codebase does have a "not bad" design in terms of ease of portability. Assuming your arch isn't VLIW I wouldn't expect too much hell. If gcc isn't a forced requirement out of the gate maybe give it a go. /* Side note: there's 2 "libdwarfs" floating around.. the one from SGI and the BSD implementation, if licensing makes any difference.. I've worked with the later https://github.com/pathscale/libdwarf-bsd */