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

Weak linkage doesn't work as expected

Note: This was originally posted on 14th May 2010 at http://forums.arm.com

I am using the weak linkage feature of the Real-View Development suite. It appears that a function that is declared as weak is replaced with a NOP regardless of whether the function actually exists in the image. My original understanding of this feature was that the weakly declared function would not be replaced with a NOP unless it was unresolved at the link stage.

Is there a linker option available to tell the linker to use a weakly defined function which has been compiled and should actually exist in the image?

Thanks in advance.

R.

Parents

Scott Douglass over 12 years ago

Note: This was originally posted on 18th May 2010 at http://forums.arm.com

If you can put all the weakly referenced functions in sections called "keepme" then you could use --keep="*(keepme)". Or you could just use --no_remove if that didn't keep too many things that you did want removed.
Cancel
Vote up 0 Vote down

Cancel

Reply

Scott Douglass over 12 years ago

Note: This was originally posted on 18th May 2010 at http://forums.arm.com

If you can put all the weakly referenced functions in sections called "keepme" then you could use --keep="*(keepme)". Or you could just use --no_remove if that didn't keep too many things that you did want removed.
Cancel
Vote up 0 Vote down

Cancel

Children

No data

Weak linkage doesn&#39;t work as expected

Weak linkage doesn't work as expected