https://sourceware.org/bugzilla/show_bug.cgi?id=18025
--- Comment #11 from Nick Clifton <nickc at redhat dot com> --- Hi Jon, > Looking at the commit, even if the object isn't rebased, every symbol without > linenumber information (e.g. type 'N' symbols) will cause an exhaustive, > linear search for the symbol (I guess leading to polynomial runtime) > > I'm not sure how to improve this. Have you tried using the latest binutils ? We did make some improvements to line number caching recent. (Although I think that this was with DWARF not STABS. Darn). > I guess the bias for all symbols in a compilation unit is going to be the > same, so there's some scope for caching that. Is there a way to reproduce this problem in a Linux environment ? (I ask because it is much easier for me to debug and fix problems in this environment). I did try uploading a copy of libstdc++.a from old cygwin installation (based upon gcc 5.4.0) and then running "nm -l" on it with a newly built x86_64-pc-cygin toolchain. It took 7 seconds to complete. So there must be something that I am doing that does not match what you are doing. 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
