Path: csiph.com!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!peer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end From: Walter Banks Newsgroups: comp.compilers Subject: Re: New experimental back end for C/C++ compiler targeting CLI Date: Wed, 31 Aug 2016 13:24:07 -0400 Organization: Aioe.org NNTP Server Lines: 31 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <16-08-017@comp.compilers> References: <16-08-007@comp.compilers> <16-08-008@comp.compilers> <16-08-009@comp.compilers> <16-08-011@comp.compilers> <16-08-012@comp.compilers> <16-08-015@comp.compilers> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: miucha.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="39924"; mail-complaints-to="abuse@iecc.com" Keywords: translator Posted-Date: 31 Aug 2016 21:52:59 EDT X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com X-Received-Bytes: 2546 X-Received-Body-CRC: 1156826633 Xref: csiph.com comp.compilers:1739 On 2016-08-30 5:48 PM, BartC wrote: > I'm mainly familiar with ASM syntax that is strictly line-oriented > and with a flat code structure. > > Then comments can either be tied to a particular instruction, or are > on their own line and might be assumed to refer to the next block of > instructions. (But then, they could be continuing a long comment > too.) > > But I'm not sure what you mean by an ASM to ASM translator; from > your other remarks it sounds like this is an ASM to C translator, > where the C is then compiled to another ASM (presumably with the > original comments?). > > It still doesn't sound that straightforward when N commented lines > in the source end up as M commented lines in output. And surely > sometimes the comments for the source ASM are meaningless on the > target? You are mostly correct. I missed making it clear that it is a subset of the problem here. The asm to asm translator goes through a C intermediary that is C transparent in that the intermediate C doesn't show in the generated listing file. What isn't transparent is some of the comments are on asm lines and others are comment blocks. It is important that these show up with the correct context even though there may be code motion in the intermediate translation. This is a subset to the problem of language to language translation unless I have missed something in this thread. w..