ARM Linker warning L6776W

Hi,

Apologies since you ran into warnings again.

In this case, the "L6439W" warning is the same as "L6776W" in a slightly different shade. 

The background is the same as explained for L6776W, where there is a symbol defined in a comdat group in two input files and the linker first selects a group from the first file but later decides to instead use a group from the second file because it is smaller or more efficient. In that case, the linker ends up with two definitions of this symbol from both groups and reported a warning about it.

This is mainly the order in which the objects are provided to the linker. Sometimes reordering the sequence in which the objects are consumed into the linker can help as the linker would spot the optimised group first then it when it encounters the group from another file it will recognise if it has selected the correct one and not fall into this situation. However we can't always control the of some objects as they come from the library and hence could run into the same again.

This is a harmless warning and should not hamper your development. We did already pick this up in our internal testing and a fix for it is on the way. We aim to have both warnings resolved in the next release which is targeted at the end of October.  

I hope this has not caused you any inconvenience and you can progress further with your development. 

Best regards,

Peterson

Hi,

Apologies since you ran into warnings again.

In this case, the "L6439W" warning is the same as "L6776W" in a slightly different shade. 

The background is the same as explained for L6776W, where there is a symbol defined in a comdat group in two input files and the linker first selects a group from the first file but later decides to instead use a group from the second file because it is smaller or more efficient. In that case, the linker ends up with two definitions of this symbol from both groups and reported a warning about it.

This is mainly the order in which the objects are provided to the linker. Sometimes reordering the sequence in which the objects are consumed into the linker can help as the linker would spot the optimised group first then it when it encounters the group from another file it will recognise if it has selected the correct one and not fall into this situation. However we can't always control the of some objects as they come from the library and hence could run into the same again.

This is a harmless warning and should not hamper your development. We did already pick this up in our internal testing and a fix for it is on the way. We aim to have both warnings resolved in the next release which is targeted at the end of October.  

I hope this has not caused you any inconvenience and you can progress further with your development. 

Best regards,

Peterson

Hi Peterson

You sent me a privat message, but I cannot reply to it as the return address is <noreply@arm.com>. Can you send me an email address to reply to you. I do not want to publish the answer to your questions here.

I have connected with you and sent you my email. Please get in touch. 

Thanks