https://sourceware.org/bugzilla/show_bug.cgi?id=22967
Nick Clifton <nickc at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |ASSIGNED
--- Comment #5 from Nick Clifton <nickc at redhat dot com> ---
Hi Martin,
> I probably incline to 3).
Actually I think that we can accommodate all three alternatives...
Imagine that there is a configure-time option to set the default
behaviour, then we add a new command line option to nm called
--ifunc-chars that behaves as follows:
--ifunc-chars=
Restores default behaviour - however that was configured.
--ifunc-chars=<char>
Use <char> for both local and global ifuncs.
It is the user's responsibility to choose a <char> that does not
conflict
--ifunc-chars=<char1><char2>
Use <char1> for global ifuncs.
Use <cahr2> for local ifuncs.
It is the user's responsibility to choose <char>s that do not conflict.
--ifunc-chars=<char1><char2><char3>
Use <char1> for global ifuncs.
Use <cahr2> for local ifuncs.
Use <char3> for indirect symbols.
It is the user's responsibility to choose <char>s that do not conflict.
Maybe nm should warn if a <char> is chosen that conflicts with another symbol
type...
I'll try to run up a patch that implements this idea, although I must admit
that
this PR does have a low priority at the moment ...
Cheers
Nick
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils
