|
|||||||||||
|
Technical Support Support Resources
Product Information |
ARMCLANG: Create C compiler listing using ARMCLANGInformation in this knowledgebase article applies to:
QUESTIONPreviously I used ARMCC v5.x compiler toolchain in MDK µVision for my project. With the option "Options for Target - Listing - C Compiler Listing: .\*.txt" enabled, compiler can generate a compiler listing *.txt file for each C module after building my project, which contains mixed-style assembly codes with the corresponding C codes.
Now, after I switch from ARMCC v5.x to ARMCLANG v6.x compiler toolchain for my project in µVision, ARMCLANG compiler doesn't generate such listing files in my objects output folder. How can I resolve this? ANSWERARMCC v5.x compiler toolchain offers such a feature to generate mixed-style compiler listing file. However, ARMCLANG v6.x compiler toolchain doesn't support such a feature. For ARMCLANG v6.x compiler creating list file for a C module actually means that clang translates the C module into an clang assembly type file which clang can then create an object from. It can be considered as an assembly level intermediate representation. As the assembly language being used by clang is different from armcc/armasm, such a listing file generated by ARMCLANG v6.x and by ARMCC v5.x does look significantly different. As a workaround solution to create an assembly file interleaved with C source code, you may use fromelf, for example: c:\Keil_v5\ARM\ARMCC\bin\fromelf.exe --disassemble --interleave=source --source_directory=test_folder test.o --output=test.lst MORE INFORMATION
Last Reviewed: Thursday, May 14, 2020 | ||||||||||
|
|||||||||||
Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.