I am using the ARM clang tool chain version 6.10.1.
The linker is showing the following warning:
Warning: L6776W: The debug frame in .debug_frame(CHostComm.o) does not describe an executable section.
I have no idea why this is coming or how to solve the problem. Do I need to change the command line parameters for the linker or change something in my code?
Thank you for the feedback. I have been able to reproduce this issue and it will be resolved in a future release. As this is a warning, can you continue your project until we resolve the issue in the next release cycle?
This is benign warning which the arm linker emits as it finds debug info which has references to an "invalid group" section. This generally happens when you code using C++ templates, the armclang organizes the code for each template iinto different groups but doesn't put the respective debug info in the same group. So if one group gets removed it leaves behind the debug info which references code from an invalid group. armclang does not produce a separate .debug_frame section for each group and hence the linker issues this warning.
We are able to reproduce this scenario and it will be resolved in a future release. Since this is a warning, you can suppress it by passing "--diag_suppress L6776W" as a linker flag which will allow you to continue with your project.
Let me know if you are still having problems.
Thank you for the explaination. I am surprised that a product with version 6.10 still has such a bug! Am I the first person to use C++ templates? This does not convince me that the tool is well tested before release.
Hi, I'm Paul Black, Product Manager for Arm Compilers.
Clearly this warning has caused some annoyance, and that's something we like to avoid - using the Arm Compiler should be a stress-free experience! The Arm Compiler is of course widely used for C++ including templates, and we devote significant effort to our testing. However compilers are complex tools and face a virtually infinite variation in incoming code, and it's inevitable that defects will sometimes slip through testing for any compiler. In this particular case, the code generated by the compiler would have been correct and high performance, but the compiler has issued a benign warning.
I appreciate that even a benign warning can be an irritation and a distraction, and I would like to thank you for bringing this to our attention. I'm always eager to hear feedback from users, and I'm always eager to talk about ways we could improve the compiler and the user experience - we'll look into how this warning slipped out under our radar.
Thank you for the reply.
I am trying to convert a project from the armcc to armclang toolchain. After a week of endless warnings and errors messages, I am still not able to link the project.
Is this the correct forum to ask about linker errors? I have been communicating with Mr. Stephen Wang from arm support, but not really getting any nearer to a solution.
Does arm have a utility simialr to the gnu objdump to analyse the contents of the object files?
Are you still having problems migrating your project from armcc to armclang?
Is there anything else I can help you with?
Here is the link to the migration guide from armcc to armclang: https://developer.arm.com/docs/100068/latest
Further documentation about armclang can be found here: https://developer.arm.com/products/software-development-tools/compilers/arm-compiler/documentation/version-6-10
>>I have been communicating with Mr. Stephen Wang from arm support
Could you provide me with the support case IDs you raised?