------- Additional Comments From shausman at trolltech dot com 2007-01-05 14:50 ------- (In reply to comment #5)
Yes. But since with --dynamic-list-cpp-typeinfo references to the global and visible variables are still bound locally we established that --dynamic-list needs to be used instead, with a script that takes care of the typeinfo symbols (as per -cpp-typeinfo) and also mentions the names of the global and exported/visible variables, so that references to them are not locally bound. Since that is a cumbersome job I'm asking in this enhancement request for a way to automate that, in hope that the linker has all the necessary information for that. I believe this applies to all static class members that have default visibility and regular global variables with default visibility. I guess there is no actual difference between those two from the linker's perspective. -- http://sourceware.org/bugzilla/show_bug.cgi?id=3831 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
