Thomas Neumann via Gcc <gcc@gcc.gnu.org> writes: >> Not all GCC/G++ targets are GNU/Linux and use GLIBC. A duplicate >> implementation in GLIBC creates its own set of advantages and >> disadvantages. > > so what should I do now? Should I try to move the lookup into GLIBC? Or > handled it within libgcc, as I had originally proposed? Or give up due > to the inertia of a large, grown system?
Just echoing what David said really, but: if the libgcc changes are expected to be portable beyond glibc, then the existence of an alternative option for glibc shouldn't block the libgcc changes. The two approaches aren't be mutually exclusive and each approach would achieve something that the other one wouldn't. Thanks, Richard
