Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.compilers > #1739

Re: New experimental back end for C/C++ compiler targeting CLI

From Walter Banks <walter@bytecraft.com>
Newsgroups comp.compilers
Subject Re: New experimental back end for C/C++ compiler targeting CLI
Date 2016-08-31 13:24 -0400
Organization Aioe.org NNTP Server
Message-ID <16-08-017@comp.compilers> (permalink)
References (1 earlier) <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>

Show all headers | View raw


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..

Back to comp.compilers | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

New experimental back end for C/C++ compiler targeting CLI Alexandre <alebencz@gmail.com> - 2016-08-25 10:40 -0300
  Re: New experimental back end for C/C++ compiler targeting CLI rockbrentwood@gmail.com - 2016-08-26 12:54 -0700
    Re: New experimental back end for C/C++ compiler targeting CLI Hans-Peter Diettrich <DrDiettrich1@netscape.net> - 2016-08-29 10:28 +0200
      Re: New experimental back end for C/C++ compiler targeting CLI BartC <bc@freeuk.com> - 2016-08-29 18:52 +0100
        Re: New experimental back end for C/C++ compiler targeting CLI Walter Banks <walter@bytecraft.com> - 2016-08-29 21:21 -0400
          Re: New experimental back end for C/C++ compiler targeting CLI Walter Banks <walter@bytecraft.com> - 2016-08-30 13:44 -0400
          Re: New experimental back end for C/C++ compiler targeting CLI BartC <bc@freeuk.com> - 2016-08-30 22:48 +0100
            Re: New experimental back end for C/C++ compiler targeting CLI Walter Banks <walter@bytecraft.com> - 2016-08-31 13:24 -0400
            Re: New experimental back end for C/C++ compiler targeting CLI Martin Ward <martin@gkc.org.uk> - 2016-09-06 18:09 +0100
        Re: New experimental back end for C/C++ compiler targeting CLI Hans-Peter Diettrich <DrDiettrich1@netscape.net> - 2016-08-30 13:13 +0200
    Re: New experimental back end for C/C++ compiler targeting CLI Walter Banks <walter@bytecraft.com> - 2016-08-29 13:15 -0400

csiph-web