[llvm-dev] [cfe-dev] RFC: Add a way to interleave source code in assembler output
Roger Ferrer Ibanez via llvm-dev
llvm-dev at lists.llvm.org
Mon Mar 13 09:30:07 PDT 2017
Hi all,
I’ve put a WIP implementation of this feature in review in
Llvm: https://reviews.llvm.org/D30897
Clang: https://reviews.llvm.org/D30898
It is still unclear how can I test this. I understand that we avoid end-to-end tests, so this looks like it should be mostly tested in the llvm side and in clang just make sure we forward the flags correctly.
Suggestions for improvements are very welcome.
Kind regards,
Roger
From: Andrey Bokhanko [mailto:andreybokhanko at gmail.com]
Sent: 05 February 2017 21:33
To: Roger Ferrer Ibanez
Cc: cfe-dev at lists.llvm.org; llvm-dev; nd
Subject: Re: [cfe-dev] RFC: Add a way to interleave source code in assembler output
Hi Roger,
I would *really* love to see this feature available -- writing in a combination of C and inline assembler is still quite common in embedded software development. Verbose asm would be a very useful tool in debugging.
...speaking on inline assembler, I wonder how your implementation works with it? Does it simply print a whole inline assembly statement (from C source code) before printing it again (from generated assembler)?
> For clang it would simply mean to add a flag like -fsource-asm or maybe extend the meaning of -fverbose-asm (like it will happen in GCC 7 but see some further comments below).
I vote for the latter. GCC is still most commonly used compiler in embedded development (for which generating assembler file is most relevant) -- the closer we are to it, the better for everyone.
Yours,
Andrey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170313/de01089d/attachment.html>
More information about the llvm-dev
mailing list