https://sourceware.org/bugzilla/show_bug.cgi?id=25355
Nick Clifton <nickc at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nickc at redhat dot com
--- Comment #1 from Nick Clifton <nickc at redhat dot com> ---
Hi Martin,
I think that this problem is due to a weakness in the plugin-api. The
specification of the ld_plugin_symbol_kind enum only has five values:
enum ld_plugin_symbol_kind
{
LDPK_DEF,
LDPK_WEAKDEF,
LDPK_UNDEF,
LDPK_WEAKUNDEF,
LDPK_COMMON
};
So it does not have a way to distinguish between code symbols and data symbols.
Hence when a defined symbol is seen the BFD library has to make a choice, and
it chooses to assume that it is a code symbol. Given that section names have
also been discarded by this point, it is impossible for the library to
distinguish between code and data symbols.
So unless we create a new version of the plugin API, I think that this will
have to remain as an unsolved problem. At least that is my take on the
subject. Lets see if anyone else has any better ideas.
Cheers
Nick
--
You are receiving this mail because:
You are on the CC list for the bug.
