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

On 2016-08-29 9:21 PM, Walter Banks wrote:
> On 2016-08-29 1:52 PM, BartC wrote:
>> I've played with source-to-source translators, and never managed
>> to deal with comments properly and in the end gave up. ...
>
> How we handled the comments on the asm to asm translation was put
> the whole sourceline into in our case a C statement // comment with
> enough parsing information to tie it as well to the generated code. A
> filter (In our case a compiler pragma) reprocessed the listing line.
> It could have been done with a small post processing program quite
> easily.
>
> It proved quite workable.


Something else to think about for comments. The source level debugging
format we often use ties generated code to both source files and
listing files. The system I described above uses this information. We
have often used this information on many different debug applications
after post processing.


In the asm to asm translations we have done it is quite strange to see a
listing file for an target processor being stepped with a source file of
the original processor.


I think then same thing could be done with elf dwarf extensions as well.


w..

Return to the comp.compilers page.
Search the comp.compilers archives again.