Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!news-out.readnews.com!news-xxxfer.readnews.com!news.misty.com!news.iecc.com!.POSTED!nerds-end From: =?ISO-8859-1?Q?Patrik_T=FAri?= Newsgroups: comp.compilers Subject: Re: Best tools for writing an assembler? Date: Thu, 20 Feb 2014 17:15:28 -0800 (PST) Organization: Compilers Central Lines: 10 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <14-02-025@comp.compilers> References: <14-02-018@comp.compilers> NNTP-Posting-Host: news.iecc.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: miucha.iecc.com 1392966982 34326 64.57.183.58 (21 Feb 2014 07:16:22 GMT) X-Complaints-To: abuse@iecc.com NNTP-Posting-Date: Fri, 21 Feb 2014 07:16:22 +0000 (UTC) Keywords: assembler, comment Posted-Date: 21 Feb 2014 02:16:22 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:1104 Thank you all. About using an existing assembler -- it's like writing Machine Description files for GCC right? Well my problem is that those stuff seemed quite complex and would take a while to understand all syntax and options, and then define all 'generalized' instructions. Any good "Getting Started" guide on that with any assembler or compiler which would make it easier to learn? [Adapting an assembler is much easier than retargeting a compiler. The assembler doesn't know anything about the semantics of instructions, just what field goes where. -John]