This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ARM Linker warning L6776W

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?

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

    Paul.

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

    Paul.

Children