Hi, thanks Danny. I really appreciate your sharing of information.
I would prefer a stripped libstdc++.a, and a non-stripped
libstdc++-debug.a with debug capability enabled. It will be very useful.
I am also wondering how GCC did the trick. I mean, how does GCC know
that string has been instantiated externally. And the mangled name is
surprisingly short, e.g. "__ZNSsC1Ev" for "std::string::string()".
Interesting but quite out of expectation.
--- Original Message from Danny Smith ---
Have you tried any of suggestions at:
In past, I have stripped libstdc++.a binaries that I have uploaded in
order to reduce size. Should I keep the stabs debug info in next time,
and let users strip if they want? Should I also produce a special debug
version of libstdc++.a (that is built in debug mode to provide
additional checks on implementation-specific and undefined behaviour) ?